WordPress.org

Forums

[resolved] 58% cpu usage (5 posts)

  1. hitmoments
    Member
    Posted 5 years ago #

    Recently after updating wordpress 2.8.4 version My server admin found that My website is using more then 60% of CUP usage of the server and that affects all the other website which are hosted on the reseller account of the server...
    has anyone faced this situation with wordpress 2.8.4?
    Currently our server admin as diaabled the account of our website which is using more then 60% of server memory.
    Any solution by which the server memory is reduced?

  2. Samuel B
    moderator
    Posted 5 years ago #

  3. fleetadmiralj
    Member
    Posted 5 years ago #

    Same problem here. My site was suspended for using 5.5x the allowable CPU and memory on the server over the weekend. Also using 2.8.4. I've been using wordpress on this server for over 2 years now and never got a warning or anything before about CPU usage.

    I'm waiting to hear back from the server about what specifics they can give me at this point. I'll probably use WP Super Cache once I can actually access my site again. At first I thought my site might have been hacked, but might this just be a WP hogging problem?

  4. bolonki
    Member
    Posted 5 years ago #

    My dedicated server had an enormous spike in CPU usage and load after upgrading to WP 2.84, as you can see in this graph. I am using SuperCache, eAccelerator, MySQL query caching, serving images statically with Nginx, and only use three plugins. Nothing changed other than the upgrade, everything else is exactly the same.

  5. kneeslider
    Member
    Posted 5 years ago #

    Server load on my dedicated server jumped immediately after upgrading to 2.84. I added super cache which doesn't seem to help.

    Working with the server crew at my ISP they said the CPU load goes up and then the server was dipping into swap space with physical RAM decreasing.

    Zero problems before the upgrades.

    Perhaps someone with deeper knowledge of WP could look at this issue since there are more than a few of us now reporting what appears to be the same problem.

Topic Closed

This topic has been closed to new replies.

About this Topic