Hi Darren,
How large is your corpus? The speed you can expect depends on how much
data you load it with. There is a graph in the package level javadocs
that shows this:
http://lucene.apache.org/java/2_4_0/api/contrib-instantiated/org/apache/lucene/store/instantiated/package-summary.html
Has anyone gotten some initial performance observations about
instantiated index?
I replaced my RAMDirectory searcher with one and it was slower or about
the same. The note about it claims 100x possible performance
improvement. Maybe there is a data size beyond which its performance
excels.
thank
Hello Karl;
This is good good good news. It works.
However, I added a document like
doc.add(new Field("f", "a", Field.Store.YES,
Field.Index.NOT_ANALYZED_NO_NORMS));
and then searched. The score is 0.3~ for the found document. should
not it be 1.0?
also it will find when searched for "f","b" o
15 sep 2008 kl. 18.51 skrev Karl Wettin:
Are the adds reflected directly to the index?
Yes. An InstantiatedIndexReader is always current.
You will probably still have to reconstruct your searcher.
I never really looked in to what happends if you don't.
The second statement was wrong. There
15 sep 2008 kl. 18.45 skrev Cam Bazz:
I have been looking at instantiated index in the trunk. Does this come
with a searcher?
Pass an InstantiatedIndexReader to the constructor of an IndexSearcher.
Are the adds reflected directly to the index?
Yes. An InstantiatedIndexReader is always cur
Hello,
I have been looking at instantiated index in the trunk. Does this come
with a searcher? Are the adds reflected directly to the index?
Or is it just an experimental thing only with reader and writer?
Best.
-
To unsubscrib
