Timeline for Performance Problem: Delay on first request
Current License: CC BY-SA 3.0
5 events
| when toggle format | what | by | license | comment | |
|---|---|---|---|---|---|
| Aug 10, 2012 at 0:32 | history | bounty ended | Clive♦ | ||
| Aug 10, 2012 at 0:32 | comment | added | Clive♦ | There were so many good answers to this question, thanks to everyone that sees this comment and contributed to the post. I thought this particular answer summed up the main issues nice and succinctly; checking these 3 points thoroughly has helped speed up Drupal sites nicely on various different machines. Thanks @MPD | |
| Aug 7, 2012 at 18:27 | comment | added | Renee | I've found almost all the (M/L/W)AMP dev stacks, even ones specifically for Drupal like Bitnami, are badly tuned or not tuned at all (I think Acquia's dev stack is the exception). And of course a default mySQL install for a production machine isn't. InnoDB logfiles are by default like 5M and memory allocated is miniscule. Often a proper tuning is all that's needed to make a site snappy - even just dropping in the my-medium.cnf or my-large.cnf is sufficient. | |
| Aug 4, 2012 at 18:46 | history | edited | mpdonadio♦ | CC BY-SA 3.0 |
added 44 characters in body
|
| Aug 2, 2012 at 20:58 | history | answered | mpdonadio♦ | CC BY-SA 3.0 |