lucene-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Simon Willnauer (JIRA)" <>
Subject [jira] [Updated] (LUCENE-4515) Make MemoryIndex more memory efficient
Date Thu, 01 Nov 2012 12:39:12 GMT


Simon Willnauer updated LUCENE-4515:

    Attachment: LUCENE-4515.patch

here is a new patch removing all the nocommits (except of the one that says I should move
IntBlockPool to o.a.l.util - I will do that before I commit).

I added more tests. Cleaned up *BlockPool and added javadocs to several places. 

MemoryIndex now only allows to reset & specify your own allocator if you are in the same
package. If you really need to do this you now can but its not public API neither guaranteed
in terms of BWCompat (it's module anyway). I think this is a fair compromise here.
> Make MemoryIndex more memory efficient
> --------------------------------------
>                 Key: LUCENE-4515
>                 URL:
>             Project: Lucene - Core
>          Issue Type: Improvement
>          Components: modules/other
>    Affects Versions: 4.0, 4.1, 5.0
>            Reporter: Simon Willnauer
>             Fix For: 4.1, 5.0
>         Attachments: LUCENE-4515.patch, LUCENE-4515.patch
> Currently MemoryIndex uses BytesRef objects to represent terms and holds an int[] per
term per field to represent postings. For highlighting this creates a ton of objects for each
search that 1. need to be GCed and 2. can't be reused.

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

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

View raw message