[
https://issues.apache.org/jira/browse/LUCENE-1219?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12623593#action_12623593
]
Eks Dev commented on LUCENE-1219:
---------------------------------
bq. did you ever measure the before/after performance difference?
sure we did, it's been a while we measured it so I do not have the real numbers
at hand. But for both cases (indexing and fetching stored binary field) it
showed up during profiling as the only easy quick-win(s) we could make .
We index very short documents and indexing speed per thread before this patch
was is in 7.5k documents/ second range, after it we run it with the patch over
9.5-10K/Second, sweet...
for searching, I do not not remember the numbers, but it was surely above 5%
range (try to allocate 12Mb in 6k objects per second as unnecessary addition
and you will see it :)
> support array/offset/ length setters for Field with binary data
> ---------------------------------------------------------------
>
> Key: LUCENE-1219
> URL: https://issues.apache.org/jira/browse/LUCENE-1219
> Project: Lucene - Java
> Issue Type: Improvement
> Components: Index
> Reporter: Eks Dev
> Assignee: Michael McCandless
> Priority: Minor
> Fix For: 2.4
>
> Attachments: LUCENE-1219.extended.patch, LUCENE-1219.extended.patch,
> LUCENE-1219.patch, LUCENE-1219.patch, LUCENE-1219.patch, LUCENE-1219.patch,
> LUCENE-1219.take2.patch, LUCENE-1219.take3.patch
>
>
> currently Field/Fieldable interface supports only compact, zero based byte
> arrays. This forces end users to create and copy content of new objects
> before passing them to Lucene as such fields are often of variable size.
> Depending on use case, this can bring far from negligible performance
> improvement.
> this approach extends Fieldable interface with 3 new methods
> getOffset(); gettLenght(); and getBinaryValue() (this only returns reference
> to the array)
>
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
