eZ Community » Forums » Extensions » Ez Find process hog
expandshrink

Ez Find process hog

Ez Find process hog

Monday 03 December 2012 5:28:24 pm - 4 replies

Ez Publish 4.4 w/Ez Flow

Hi. I managed to install EZ Find / Solr as I was said it will lower server load and take better search solutions. But in fact it is getting server load worse. We ran everything as the ezFind official documentation says. I configured delayed index content in site.ini, and all that stuff. We indexed everything for the first time (+40,000 articles) and then configured cronjobs to work at every 30 minutes as we upload We upload around 150 articles daily.

The problem is that this cronjobs:

/usr/local/bin/php runcronjobs.php -s ezfindexcontet

/usr/local/bin/php runcronjobs.php -s ezfoptimizeindex

will take about 95% of processor load (each one) and will double total server load. Also, I thought that cronjobs will run and every 30 min then stop process when finished and then run again in 30 minutes and stop etc etc. but they are not. They will remain running as a permanent process.

For example cronjob ezfoptimizeindex was set up to run at 5 o'clock and its still running after 5 hours. Same for ezfindindexcontent.

What am I doing wrong? or what is going wrong? does anybody knows? is it a bug, something wrong? where should I look for? Thanks.

.

Monday 03 December 2012 5:58:44 pm

Hi,

First check if solr has enough memory. It really likes a lot of memory, so maybe it is logging "out of memory" somewhere happy.gif Emoticon

If you are using optimize cronjob then you don't need the OptimizeOnCommit option in ezfind.ini (which is enabled by default). Did you disabled it?

Monday 03 December 2012 9:00:08 pm

Quote from Ivo Lukač :

Hi,

First check if solr has enough memory. It really likes a lot of memory, so maybe it is logging "out of memory" somewhere happy.gif Emoticon

If you are using optimize cronjob then you don't need the OptimizeOnCommit option in ezfind.ini (which is enabled by default). Did you disabled it?

Great tips... I will check memory... 

I configured cronjobs because I noticed a lot of people complaining about slow publishing when indexing and optimizing on commit. I disbled optimize on commit but now I have a question: What does optimize on commit does?

Monday 03 December 2012 9:53:28 pm

Quote from Luis D Garcia :
Quote from Ivo Lukač :

Hi,

First check if solr has enough memory. It really likes a lot of memory, so maybe it is logging "out of memory" somewhere happy.gif Emoticon

If you are using optimize cronjob then you don't need the OptimizeOnCommit option in ezfind.ini (which is enabled by default). Did you disabled it?

Great tips... I will check memory... 

I configured cronjobs because I noticed a lot of people complaining about slow publishing when indexing and optimizing on commit. I disbled optimize on commit but now I have a question: What does optimize on commit does?

Optimize optimizes indexes, so it is not really important to run is after each commit. Rather do it will separate script like you do it, but then disable it on each commit to really make the difference. Commit is something necessary for changes to take effect in the index. It can also be applied to batch commands but that is another story.

Give more memory to solr and try the OptimizeOnCommit on disable, test everything again.  

Tuesday 04 December 2012 12:05:05 pm

For optimal performances, I generally recommend to:

- set up delayed indexing

- use optimizeoncommit=off

- run the optimize cronjob not more frequently than once a day - you can set schedule its execution at nighttime if your audience is not coming in 24h/day

Btw, with 150 articles / day, the ezfindexcontent script should not really take that much time to execute. Does it?

Last piece of advice: running ezfind with solr on the same server as the website will actually not decrease the load, but rather the opposite, as you will be running 2 apps instead of one.

The main selling point for ezfind is the much (much) better search capabilities (facets, filters, sorting, linguistic support, custom fetches, etc... too many to list here). If you want better performances you should dedicate a separate server to Solr (in general terms, just treat it like you would a database)

expandshrink

You must be logged in to post messages in this topic!

36 542 Users on board!

Forums menu

Proudly Developed with from