ExpressionEngine CMS
Open, Free, Amazing

Thread

This is an archived forum and the content is probably no longer relevant, but is provided here for posterity.

The active forums are here.

troubleshooting intermittent slow page load

March 19, 2012 8:34pm

Subscribe [3]
  • #1 / Mar 19, 2012 8:34pm

    nadea.c

    83 posts

    I’m familiar with best practices in optimizing pages to load up quickly, but I know very little about all the other factors that can cause pages to load slowly.

    In trying to better understand how to troubleshoot slow page load on EE sites, I’ve read Greg Aker’s helpful article Troubleshooting Site Performance Issues, and I’ve turned on the Output Profiler and Template Debugging.

    I’m baffled, though, about intermittent slow loads. For example, there’s a page on one of my sites that typically loads in 3-5 seconds, but every once in a while, it will take more than 25 seconds to load. Because the page regularly loads in just a few seconds, I’m inclined to think that the cause of the now-and-again whopping page load time is not in the template—does that logic hold, or am I missing something?

    In instances where the page takes a very long time to load, I’m also observing that the Total Execution Time benchmark in the Output Profiler is several times longer. The database query times, however, don’t seem to be correlated in this way.

    I’m wondering if these datapoints are indicative of the PHP server being taxed?

    Once again, I’m new to this stuff and greatly appreciate any guidance and advice. Thanks!

  • #2 / Mar 21, 2012 12:16pm

    Shane Eckert

    7174 posts

    Hello nadea.c,

    I am sorry to hear you are running into this snag.

    You logic seems sound. I might not rule out the template yet though. Is this the only page that hit’s the 25 seconds issue?

    Did you happen to notice anything else in the output of the debug? Were there more queries being run at that time than other times?

    What is in that template? Anything special? Is PHP enabled and being used?

    Another angle to approach this from is the server. Next time this happens note the time. Then ask your hosting provider to check the Apache logs for that time frame to see if there are errors or anything that might help us. Also have them check system logs for messages. They probably already monitor for processes that were spiking or pegged. Maybe SQL server is not happy, or some other rouge process is sucking up processor time. You could ask them if their monitoring software caught anything.

    Hopefully this gives you a few different things to check out. Please let me know what you find.

    Cheers!

.(JavaScript must be enabled to view this email address)

ExpressionEngine News!

#eecms, #events, #releases