I tried to profile script and got some very strange results. For test i made index from 2000 documents. Index was 6MB in size and optimized.
Xdebug made ~500MB large cachegrind file! Is that normal? When I opened that file with KCacheGrind result was: http://prcentrs.lv/kca.png Tests were executed on my notebook - so on server they would run faster. But even on notebook (dualcore cpu, 2gb ram) it shouldnt take more than minute to finish. Can anyone understand something from that cachegrind report and tell me - what is wrong with my script and/or index. If that helps - i'm using: Zend_Search_Lucene_Analysis_Analyzer::setDefault( new Zend_Search_Lucene_Analysis_Analyzer_Common_Utf8_CaseInsensitive()); Endijs Stefan Oestreicher-3 wrote: > > 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 > > > -- View this message in context: http://www.nabble.com/Zend_Search_Lucene---how-to-find-performance-problem-source--tp20085562p20092853.html Sent from the Zend Framework mailing list archive at Nabble.com.
