By Cosmy on
Hi all, I have a drupal/pressflow core with innodb tables and a boost module for caching. There are several users that insert around 100 nodes by day.
The site speed is quite average but saving and updating nodes is a very very slow process.. from 30 seconds to minutes.
I don't know why it is so slow. I've noticed that afer clicking save button, while the edit page is still loading, if I access the node the modifies are made but the admin page still loads.
It's very strange and frustrating for whom work in the admin pages. Do you have any idea on how to correct this behaviour and what to do, or how to find the real problem?
(sorry for my poor english)
Comments
I remember another user
I remember another user coming across this before. I believe the culprit was the XML Sitemap module. If you do happen to have this module installed, try disabling to see if that speeds things up. If it doesn't you might want to try to disable some modules one at a time to see if any of the other ones are the reason for the slow updates.
To speed things up, you could possibly look at the slow query logs from mysql and see if you can find the query that is slowing things down. Since you said the content is available before the admin page finishes loading, I'm willing to bet it's going to be a caching/log table query that is slow.
Hope this helps!
-= Gerrit Brands
I've uninstalled XML sitemap
I've uninstalled XML sitemap module long time ago, with all the other non-essentials (all but "locale" module because i need italian).
Of course I've seen slow queries log and they are all about boost_cache entries (select, delete and update), but i need boost to serve anonymous users without slow down or collapsing.
I've found out
I've disabled the boost module and now the site is very performing in insert and update.. (The problem will come when there will be a lot of connections in a day)
Is it a Boost module problem?
It sounds like Boost was the
It sounds like Boost was the culprit. You may want to file an issue with the module and see if anyone responds to your problem there. I'm sorry, but I'm not too familiar with that module and not too sure on where to go next other than to the issue queue.
One thing you could try to do, if you absolutely have to have boost running and a quick administrative save, would be to hack the Boost module and see if you can disable the caching occurring on node save and insert. I believe it would be in the function called boost_nodeapi(). Again, this is a hack and will be overwritten if you update the module and may have unintended consequences. Try it on a test site first to be sure it will work for your use-case.
-= Gerrit Brands
Boost has some "dangerous"
Boost has some "dangerous" check boxes to flush cache on certain events. If you need to use Boost again, enable it and uncheck 'clear cach and views cache on node insert' . Not the exact words but similar.
What's new and changing in PHP 8.4
works well after flushing
at the moment i've flushed the boost_cache tables and than re-activate it... and now the site is going well (with an average of 50 apache connections per second).
I think the real problem is that when the cache grows (after a week it has thousands of entries) it has to manage everytime you insert a field a huge amount of db lines (deleting, updating and reinserting everything, because of homepage views updating).
So i'll open an issue on boost module, but the solution is to flush cache tables every night.
before the issue, try setting
before the issue, try setting cache lifetime to to a lower value.
What's new and changing in PHP 8.4
It was 15 minutes, the less
It was 15 minutes, the less possibile.. i think the problem was just the short time. The shorten it is, the more frequently it has to do a lot of deletes and new cache generation inserts and updates.
Now i'll try not to flush the cache for days and see what happens
Those checkboxes were the ones
You don't know how much your comment helped me. I solved a huge problem I was having, a newspaper (posting all the time) website was running very very fast but no create or edit was working.
Thank you so much!
Cache Expire
I had the same problem and did not have Boost enabled.
Problem ended up being Cache Expire module as it was expiring cache for multiple pages on node insert. Simply unchecked "node insert" under actions and it improved it significantly.
This works!
This works fine for me. I unchecked some configuration checkboxes and load time decrease from 20secs to 2,5secs.
Thanks a lot!