lucene-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Grant Ingersoll (JIRA)" <>
Subject [jira] Commented: (LUCENE-550) InstantiatedIndex - faster but memory consuming index
Date Sun, 24 Feb 2008 03:19:19 GMT


Grant Ingersoll commented on LUCENE-550:

Did zOlive ever post his code Jakarta Commons?  Without him actually doing it, I don't know
that it is good enough legally to accept it.

Also, is your last comment such that you think there is a new patch?

> InstantiatedIndex - faster but memory consuming index
> -----------------------------------------------------
>                 Key: LUCENE-550
>                 URL:
>             Project: Lucene - Java
>          Issue Type: New Feature
>          Components: Store
>    Affects Versions: 2.0.0
>            Reporter: Karl Wettin
>            Assignee: Grant Ingersoll
>         Attachments: HitCollectionBench.jpg, LUCENE-550_20071021_no_core_changes.txt,
> Represented as a coupled graph of class instances, this all-in-memory index store implementation
delivers search results up to a 100 times faster than the file-centric RAMDirectory at the
cost of greater RAM consumption.
> Performance seems to be a little bit better than log2n (binary search). No real data
on that, just my eyes.
> Populated with a single document InstantiatedIndex is almost, but not quite, as fast
as MemoryIndex.    
> At 20,000 document 10-50 characters long InstantiatedIndex outperforms RAMDirectory some
> 15x at 100 documents of 2000 charachters length,
> and is linear to RAMDirectory at 10,000 documents of 2000 characters length.
> Mileage may vary depending on term saturation.

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:
For additional commands, e-mail:

View raw message