Timeline for Painfully slow, Devel Query logs show culprit
Current License: CC BY-SA 3.0
6 events
| when toggle format | what | by | license | comment | |
|---|---|---|---|---|---|
| May 11, 2016 at 17:01 | comment | added | Collins | No errors to be found in watchdog, and no recent changes to modules. Im going to download everything and set up in WAMP and see how the speeds are there | |
| May 11, 2016 at 16:55 | comment | added | Neograph734 | Is one of your modules throwing lots of errors? There excess database queries can cause slowdowns. | |
| May 11, 2016 at 16:45 | comment | added | Collins | I have 8 drupal sites on this server, all with databases on the same server, and the other 7 sites are insanely quick. Its just this one that is slow, and yeah it happened within a few days, with nothng I can think of to spur it | |
| May 11, 2016 at 16:44 | comment | added | danielson317 | Also if you don't care about the data in the table, User last read this, new node for this user, and other such features, You can write a cron to only keep the last 10 thousand entries Similar to what the system log does. Warning! you will be deleting real and valuable data. So be very sure you don't need it. | |
| May 11, 2016 at 16:40 | comment | added | danielson317 | Beat me to the answer. But I would like to add. With several thousand nodes (say 2000) and 10000 users that up to 20 Million entries in that table. That's kind of big. Consider partitioning the table to increase performance. Not entirely sure how to do that with Drupal but I'm confident it's supported. | |
| May 11, 2016 at 16:36 | history | answered | Neograph734 | CC BY-SA 3.0 |