Sorry, I completely overlooked that bit of your email. I'm not sure
about the bottleneck in that case... it might be your hosting provider
with a (very, very) slow server? An index as small as ~7350 docs and a
limit of 150 results should be lightning fast...
You can speed up your indexing process by the way. Just let it index
all documents and do one optimze() afterwards.
On Oct 21, 2008, at 15:51 , Endijs Lisovskis wrote:
Thanks for your response. At least someone :)
But your suggestion will not make any difference in performance,
because, as
I said in first email index IS optimized.
Maybe there are some potential problems with index if data is in
UTF8 ?
How to trace - where to look for problem?
Index was made in this manner: select first 1000 articles -> add to
index ->
optimize, select next 1000 articles -> add to index -> optimize. Of
course:
1 article = 1 document. At the end index is optimized and consists
from
~7350 documents.
I hope someone can help.
Endijs Lisovskis
Jurriën Stutterheim wrote:
Hi,
You should probably optimize your index before searching (and make
sure it stays optimized, using a Cron-job).
See
http://framework.zend.com/manual/en/zend.search.lucene.index-creation.html#zend.search.lucene.index-creation.optimization
for more details on how to do this =)
- Jurriën
--
View this message in context:
http://www.nabble.com/Zend_Search_Lucene---how-to-find-performance-problem-source--tp20085562p20090740.html
Sent from the Zend Framework mailing list archive at Nabble.com.
