lucene-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Artem Vasiliev (JIRA)" <>
Subject [jira] Commented: (LUCENE-769) [PATCH] Performance improvement for some cases of sorted search
Date Wed, 10 Jan 2007 19:34:27 GMT


Artem Vasiliev commented on LUCENE-769:

Also tried this with DOCS_NUM == 1,000,000. Right after index creation it was 
    [junit] 1687ms elapsed for DocCaching sort
    [junit] 1922ms elapsed for FieldCache'd sort

But next 2 time I ran it (without index set up) the timings were near this:
    [junit] 94ms elapsed for DocCaching sort
    [junit] 1797ms elapsed for FieldCache'd sort

> [PATCH] Performance improvement for some cases of sorted search
> ---------------------------------------------------------------
>                 Key: LUCENE-769
>                 URL:
>             Project: Lucene - Java
>          Issue Type: Improvement
>    Affects Versions: 2.0.0
>            Reporter: Artem Vasiliev
>         Attachments: DocCachingSorting.patch
> It's a small addition to Lucene that significantly lowers memory consumption and improves
performance for sorted searches with frequent index updates and relatively big indexes (>1mln
docs) scenario. This solution supports only single-field sorting currently (which seem to
be quite popular use case). Multiple fields support can be added without much trouble.
> The solution is this: documents from the sorting set (instead of given field's values
from the whole index - current FieldCache approach) are cached in a WeakHashMap so the cached
items are candidates for GC.  Their fields values are then fetched from the cache and compared
while sorting.

This message is automatically generated by JIRA.
If you think it was sent incorrectly contact one of the administrators:
For more information on JIRA, see:


To unsubscribe, e-mail:
For additional commands, e-mail:

View raw message