Tuesday 22 September 2009 2:34:39 am

Do you have many attributes of type ezkeyword (which automatically relates objects to each other)? This is a known performance hog because of infinite loops.

eZ Publish certified developer
http://auth.ez.no/certification/verify/392313

Tuesday 22 September 2009 5:11:11 am

Hi Martin

What ezp version are you using? MyISAM is in every aspect a bad choice and not supported

What the relation is with ez find and the performance problem:

- if it is for indexing
- or browsing/searching
- or both?

otoh, the slow indexing may be due to:
- not using the dedicated Solr indexing script ( extension/ezfind/bin/php/updatesearchindexsolr.php )
- a bug in ez find 2.0 where teh spell checker is rebuilt on every "commit" to Solr

...

But I need to know more details to help you out on this

Paul

eZ Publish, eZ Find, Solr expert consulting and training
http://twitter.com/paulborgermans

Tuesday 22 September 2009 6:55:49 am

First of all enable DelayedIndexing.

http://www.linkedin.com/in/ivolukac
http://www.netgen.hr/eng/blog
http://twitter.com/ilukac

Tuesday 22 September 2009 9:42:36 am

A few things to improve the speed and large sites:

- in [IndexOptions] set OptimizeOnCommit=disabled. Then configure an additional cron that calls the script extension/cronjobs/ezfoptimizeindex.php once a day or so (during low traffic hours)

This is most probably going to solve most performance problems

For additional performance gains:

- patch the solr.war file with the one from trunk in extension/ezfind/java/webapps/solr.war
- check that the spellcheck configuration is set to rebuild upon optimize in extension/ezfind/java/solr/conf/solrconfig.xml (this is the default, but may not work until you patched solr.war)

This otherwise also causes high CPU load, as the spell chek index would otherwise be built on every object update (and with several 100k of objects, that takes a lot of time)

Abut delayed indexing: this should not be much of a concern with the above changes, but in any case, you should use the ezfind provided cronjob ezfindexcontent.php (to be run rather regularly, like every 10 minutes) in combination with the daily optilize cronjob

hth
Paul

eZ Publish, eZ Find, Solr expert consulting and training
http://twitter.com/paulborgermans

Wednesday 23 September 2009 12:35:14 pm

I second Paul about optimizeoncommit setting. We had this problem until we disable it. from then, we have delayed indexing disabled but good perfomance too.

Thursday 27 January 2011 3:59:09 am

Hello everyone,

I have still a problem on this : In fact my speed problem were totally resolved with the modifications in ezfind.ini mentionned above but the solr index isn't updated after running :

php runcronjobs.php -q -s siteaccess ezfindexcontent 2>&1

My question is : What exact cronjob script is supposed to run to update the solr index every 10 minutes ?

Documentation says "run a cronjob if you delay indexing" but never mention explicitly which cronjob.

When i read the ezfindexcontent code i seems to wait for lines inside ezpending_actions sql table to know which objects to process.

Given this my second question is : Why this table is always empty after an admin content publish when "OptimizeOnCommit=disabled" ?

My third question is : Do i need to manually insert a line in ezpending_actions to fire solr index update ?

I find no documentation on this, any help would be great.

Cheers

EZP is Great

Saturday 29 January 2011 3:02:23 am

Thank you Gaetano for this clear debugging process.

It works after setting DelayedIndexing=enabled in site.ini.

Thanx !

EZP is Great