Long page load times, seems index-related
Permalink
My site has had some problems with exceptionally long page load times (40+ seconds) on certain pages in our community section (blogs, etc). Caching is disabled in the back-end. I managed to fix the problem by dumping the database, dropping it, and then reloading it, which makes me think that something messed up the mysql index file...however, since this is the second time this has happened in 4 weeks, I'd like to see what's causing this.
mysql showprocesslist was showing a very long SQL query that was regularly taking long intervals (unfortunately I don't still have the query fragment), and on both occasions on which this happened, the problem occurred suddenly (suddenly taking 40+ seconds after working normally, rather than gradually taking longer with time).
Has anyone observed this behavior before?
mysql showprocesslist was showing a very long SQL query that was regularly taking long intervals (unfortunately I don't still have the query fragment), and on both occasions on which this happened, the problem occurred suddenly (suddenly taking 40+ seconds after working normally, rather than gradually taking longer with time).
Has anyone observed this behavior before?
I'm curious to know if you have your site on shared hosting?
Also, the pages that you have the issues with (40+ sec load times) it might be helpful to list the block types you have on those pages. Perhaps the issue isn't with the core and instead with a plugin/addon you might be using. Of course including any log/errors is always helpful.
I have noticed some (in my opinion) really long load times on a site I recently did using C5. However the long loads were typically at the first request for a page, then subsequent requests were faster. The other long loads would be on a GoDaddy share hosting environment. I had the same site on my development equipment and everything popped(even while browsing external of the network).
I think the difference has to do with shared resources, as well as a separate machine for the mysql database.
So I feel that if the same code worked better in one place than the other with the same configurations and content. The equipment and equipment configuration would be the place to look for the problem.