lucene-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Michael McCandless (JIRA)" <>
Subject [jira] [Resolved] (LUCENE-4227) DirectPostingsFormat, storing postings as simple int[] in memory, if you have tons of RAM
Date Fri, 20 Jul 2012 14:49:35 GMT


Michael McCandless resolved LUCENE-4227.

       Resolution: Fixed
    Fix Version/s: 5.0
> DirectPostingsFormat, storing postings as simple int[] in memory, if you have tons of
> -----------------------------------------------------------------------------------------
>                 Key: LUCENE-4227
>                 URL:
>             Project: Lucene - Java
>          Issue Type: Improvement
>            Reporter: Michael McCandless
>            Assignee: Michael McCandless
>             Fix For: 4.0, 5.0
>         Attachments: LUCENE-4227.patch, LUCENE-4227.patch, LUCENE-4227.patch
> This postings format just wraps Lucene40 (on disk) but then at search
> time it loads (up front) all terms postings into RAM.
> You'd use this if you have insane amounts of RAM and want the fastest
> possible search performance.  The postings are not compressed: docIds,
> positions are stored as straight int[]s.
> The terms are stored as a skip list (array of byte[]), but I packed
> all terms together into a single long byte[]: I had started as actual
> separate byte[] per term but the added pointer deref and loss of
> locality was a lot (~2X) slower for terms-dict intensive queries like
> FuzzyQuery.
> Low frequency postings (docFreq <= 32 by default) store all docs, pos
> and offsets into a single int[].  High frequency postings store docs
> as int[], freqs as int[], and positions as int[][] parallel arrays.
> For skipping I just do a growing binary search.
> I also made specialized DirectTermScorer and DirectExactPhraseScorer
> for the high freq case that just pull the int[] and iterate
> themselves.
> All tests pass.

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


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

View raw message