I've been doing some "final" performance testing of 2.3RC1 and
uncovered a fairly serious bug that adds a large fixed CPU cost when
documents have any term vector enabled fields.
The bug does not affect correctness, just performance.
Basically, for every document, we were calling Arrays.fill(0) on a
large (32 KB) byte array when in fact we only needed to zero a small
part of it. This only happens if term vectors are turned on, and is
especially devastating for small documents.
|Status||Open [ 1 ]||Resolved [ 5 ]|
|Resolution||Fixed [ 1 ]|
|Status||Resolved [ 5 ]||Closed [ 6 ]|
|Workflow||jira [ 12420613 ]||Default workflow, editable Closed status [ 12562460 ]|
|Workflow||Default workflow, editable Closed status [ 12562460 ]||jira [ 12584767 ]|
|Transition||Time In Source Status||Execution Times||Last Executer||Last Execution Date|
|4h 19m||1||Michael McCandless||10/Jan/08 18:23|
|14d 9h||1||Michael Busch||25/Jan/08 03:24|