Forums / Install & configuration / RemoveObject is very slow
Håkan Bergman
Friday 17 September 2010 6:15:01 am
Hello,
I have a site that behaves akwardly when removing multiple objects.
From admin it redirects normally to content/removeobject, and when I delete 1 object it takes a lot of time, but it succeeds. When I choose 2 or more objects, it takes just as long, but the page seem to "time out", returning a blank page. It is only affecting this installation, other installations on same server with same PHP settings works normally.
So is there something in an ini-file that I have been enabled to cause this behaviour or is there other things that cause this behaviour?
Best regards,
Matthieu Sévère
Friday 17 September 2010 6:33:17 am
Hi Hakan,
It may be because you have eZ Find activated and it delete the record in the index + the object. If yes, you may consider the delayIndexing option of eZ Find
-- eZ certified developer: http://ez.no/certification/verify/346216
Gaetano Giunta
Saturday 18 September 2010 5:46:04 am
Unfortunately deindexation upon object removal is not delayed - I think its is a safety measure: whil it is ok not to find existing objects when seraching, if you find unexisting ones you will generally be upset.
So to avoid sending stuff to ezfind upon removal, the only way is to temporarily set the indexation engine to standard (deactivate ezfind) (imho a NULL indexing engine would be a good idea to impprove batch inserts/deletes).
Principal Consultant International Business Member of the Community Project Board
Saturday 18 September 2010 5:57:38 am
Gaetano, delayed delete doesn't exist in Solr, but you can use the "disableDeleteCommit" settings in eZ Find (http://ez.no/doc/extensions/ez_find/2_2/basic_configuration/configuration_settings_ez_find) and set up a frequent cronjob to commit object deletion in the index.
Tuesday 21 September 2010 1:08:50 am
Thanks for the input.
I do have Ez Find active but I don't really see how to enable the delyed indexing in the manual.
All I found out was to enable DelayedIndexing in SeachSettings in settings/override/site.ini file.
I added the following line under [SearchSettings]:
DelayedIndexing=enabled
I still get the timeout.
Are there other options I need to enable/disable in order for it to work properly?
Tuesday 21 September 2010 1:15:46 am
As the problem is more when deleting an object you should enable the settings "disableDeleteCommit" as suggested in the post above.
Friday 24 September 2010 2:20:02 am
I now use:
DelayedIndexing=enabled (settings/override/site.ini)
DisableDeleteCommits=true (settings/ezfind.ini (ezfind extension))
It is still very slow.
Do I need to have the ezfind engine running? Can that cause this problem?
At the moment this is on a test server and I don't run the java engine 24/7, only when testing it.