Are you storing document contents in the index? This will degrade performance badly in my experience (the bigger the docs, the worse the performance). If that's not the case, I'd suggest to profile your application with xdebug. This should reveal the culprit in no time.
best regards, Stefan -----Ursprüngliche Nachricht----- Von: Endijs Lisovskis [mailto:[EMAIL PROTECTED] Gesendet: Dienstag, 21. Oktober 2008 15:52 An: [email protected] Betreff: Re: [fw-general] Zend_Search_Lucene - how to find performance problem source? 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.
