lucene-java-user mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Cocula Remi" <>
Subject RE: question on Hits.doc
Date Mon, 13 Sep 2004 09:09:25 GMT

I recently had the same kind of problem but it was due to the way à was dealing with Hits.
Obtaining a Hits object from a Query is very fast. but then I was looping over ALL the hits
to retrieve informations on the documents before displaying the result to the user.
It was not necessary because in my case, the display of search results is paginated.
Now I extract documents from Hits "on demand" (ie only the few ones I need to display a page
of results). It's much more better.

-----Message d'origine-----
De : []
Envoyé : samedi 11 septembre 2004 00:20
À :
Objet : question on Hits.doc

Hey guys,

We were noticing some speed problems on our searches and after adding some
debug statements to the lucene source code, we have determined that the
Hits.doc(x) is the problem.  (BTW, we are using Lucene 1.2 [with plans to
upgrade]).  It seems that retrieving the actual Document from the search is
very slow.

We think it might be our "Message" field which stores a huge amount of text. 
We are currently running a test in which we won't "store" the "Message" field,
however, I was wondering if any of you guys would know if that would be the
reason why we're having the performance problems?  If so, could anyone also
please explain it?  It seemed that we weren't having these performance
problems before.  Has anyone else experienced this?  Our environment is NT 4,
JDK 1.4.2, and PIIIs.

I know that for large text fields, storing the field is not a good practice,
however, it held certain conveniences for us that I hope to not get rid of.


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

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

View raw message