• emalen

    (@emalen)


    Hey All,

    I have a site running on wordpress.

    My server has shut me down because to quote them:

    “The issue was that your MySQL queries were overloading the server, which is why you were temporarily bursted. Once MySQL begins to use a large portion of resources to run its queries, your database is then bursted to a MySQL Container.”

    They say that

    “The first step in preventing this from happening again, would be to optimize your code. It is very important to configure mysql to have optimal performance. This is the reason you have used so many GPU’s. “

    I don’t understand why I’m having so many issues. I have a site that gets 10,000 hits a day — which by no means is a crazy amount. Yet no server can seem to handle my site. I recently switched off godaddy to a company that would be able to host me, yet still that hasn’t helped.

    I’m using a wordpress template, no video, very few images. Yet my site seems to be cursed.

    Can anyone take a look at tell me what i’m doing wrong please.

    my site is https://www.thetvaddict.com

    Any assiatance is appreciated oh so much, as I work incredibly hard on my site yet nothing seems to be working!

Viewing 4 replies - 1 through 4 (of 4 total)
  • hello

    i have teh same problem with more tahn 10 000 hits on a single wordpress homepage Did you have a clue where it comes from?
    and what is your ne xhost provider? mine says they will close the accoiubt ??

    Moderator Samuel Wood (Otto)

    (@otto42)

    www.ads-software.com Admin

    WordPress usually takes about 12-20 queries to make a single hit. This is by no means excessive. However, when hosts overload database servers by having it host databases for thousands of sites, then yeah, it’s going to be a problem at some point.

    If you have a serious website making serious bank, then you really should get a dedicated server. Then it can run its own database and its own stuff and they can’t complain to you about it.

    However, if the site isn’t paying enough to justify that sort of expense, then there is a workaround that satisfies most people’s needs: Caching.

    The most common cache is WP-Cache. However, the current best caching system is WP-Super-Cache. Either one of these will reduce the number of SQL queries to virtually nothing by comparison. Instead of every hit making 20 queries, 99.99% of the hits will take zero queries, since it serves from the cache.

    What about the admin side of things?

    (1) I found that the autosave was hammering one of my sites on a shared server, when spending a bit of time writing a post there (maybe half an hour, with some research etc). I’ve never seen a configurable option to turn it off, but it would be a help for sites with query caps. The autosave also seems to fire plugins like the sitemap creation, which means even more queries on the admin side.

    I got around it by creating a small plugin to make the autosave timer so large as to effectively disable it, but wouldn’t an admin setting be more appropriate?

    (2) Now it’s off, the limit is no longer being reached, but I have still seen a few of what I would call redundant queries on things like the post management pages, particularly regarding the taxonomy.

    I upgraded to the latest 2.4 development code to see if any changes had been made, but nothing that I can really spot. I’ve never really looked into the admin side of things, but it could use a bit of a trimming down, and combining of queries.

    Example of queries performed on 1 post-new.php load:

    https://www.simonemery.co.uk/wp-logs/post-new.txt

    NearlyFreeSpeech.net will give you your own MySQL process. Cheaper than a dedicated server.

Viewing 4 replies - 1 through 4 (of 4 total)
  • The topic ‘WordPress Issue: Too many Mysql Queries’ is closed to new replies.