IndexSearcher

This doesn't really address your question, but...

Once you have the single indexsearcher, do you need any
others?   Could
your app just use the single instance?  

-----Original Message-----
From: Gus Kormeier [mailto:guskaltrec.com] 
Sent: Wednesday, February 22, 2006 11:28 AM
To: java-userlucene.apache.org
Subject: IndexSearcher

Maybe too general a question, but is there anything about
creating an
IndexSearcher( directory) object that would make the
instantiation
really
slow?


I have one index where the instantiation is very fast, to
the point
where I
don't need to do any pooling.  A new index I have created,
takes a very
long
time to create the IndexSearcher object.  With a 30mb index,
it can take
about 30 seconds just to instantiate an IndexSearcher().  It
almost
seems
like it is reading the index at that point.


The only difference between the indexes has been the # of
fields
indexed.
The newer one only having one field indexed.

Any ways to speed up that instantiation? Or do I have to use
a pooling
system?

Thanks for any suggestions,
-Gus

------------------------------------------------------------
---------
To unsubscribe, e-mail: java-user-unsubscribelucene.apache.org
For additional commands, e-mail: java-user-helplucene.apache.org


------------------------------------------------------------
---------
To unsubscribe, e-mail: java-user-unsubscribelucene.apache.org
For additional commands, e-mail: java-user-helplucene.apache.org