• Hello Team,

    We are experiencing a persistent CPU usage issue in our WordPress environment. Over the past week, CPU utilization on our server has frequently reached 90–100%. When it hits 100%, the site becomes unresponsive until the server is restarted.This behavior started recently without any major changes to the application code. We have monitoring set up, and it consistently reports CPU saturation during peak usage periods.I would like to ask:

    1. Have there been any known cases where WordPress sites experienced similar CPU spikes?

    2. What steps or optimizations would you recommend to investigate and resolve this?

    3. Could certain plugins, themes, or background processes trigger such sustained CPU load?

    We cannot share private or infrastructure-specific details, but I can provide general configuration or plugin/theme information if required.Any guidance or prior experiences would be greatly appreciated.

    Thanks,
    Dilip

Viewing 3 replies - 1 through 3 (of 3 total)
  • Moderator Jan Dembowski

    (@jdembowski)

    Forum Moderator and Brute Squad

    Moved to Fixing WordPress as you raised the topic in the wrong sub-forum.

    These questions are not useful and won’t help you.

    1. Have there been any known cases where WordPress sites experienced similar CPU spikes?

    2. What steps or optimizations would you recommend to investigate and resolve this?

    3. Could certain plugins, themes, or background processes trigger such sustained CPU load?

    If you want to sort out your site’s problem then you will need to focus on your site’s details and not just ask open questions like that.

    We cannot share private or infrastructure-specific details

    Then no one can possibly help you here. There are thousands of host/plugins/php combinations and those details could help sort out your issues.

    This is a bit of a deep dive but this article may help you at a high level.

    https://developer.ww.wp.xz.cn/advanced-administration/performance/optimization/

    But without specifics about your site, please do not expect any changes to your site’s performance.

    Hi Dilip,

    Agree with Jan, it’s hard to be definitive without more context. That said, these symptoms are fairly common, and if the website itself is healthy, it’s worth looking at a few other angles:

    1) Hosting environment factors

    • Scheduled backups, snapshots, or other maintenance at the hypervisor level.
    • Resource contention from other tenants on the same hardware (in shared hosting/VPS scenarios).

    2) External traffic patterns

    • Unusual spikes from bots, crawlers, or brute-force/DDoS attempts.
    • Repeated hits to wp-login.php, xmlrpc.php, or specific API endpoints.

    3) Broader stack review

    • Sometimes focusing solely on WordPress misses the underlying cause.
    • A full-stack review from network traffic and server processes to application-level activity often reveals the “smoking gun.”

    What I’d do next:

    • Check if CPU spikes align with hosting backups/snapshots or WP-Cron events.
    • Look for unusual user-agents and high request rates to /wp-login.php or xmlrpc.php.
    • Add caching if not already to reduce load on PHP/MySQL processes (page + object cache).
    • During an incident, run top/htop to see which server processes are running hot.
    Thread Starter dilipp

    (@dilipp)

    Hi Jan,

    Thank you for your time, guidance, and the detailed suggestions. We truly appreciate the effort you’ve put into helping us.

    As our application is hosted on an internal intranet environment, there are certain infrastructure-specific details we’re unable to share publicly for security reasons. However, we’ve noted all your recommendations and will work through them to troubleshoot and address the issue.

    We’ll keep you updated on our progress and get back to you after testing these suggestions.

    Thanks again for your valuable support.

    Regards,
    Dilip.

Viewing 3 replies - 1 through 3 (of 3 total)

The topic ‘High CPU Usage Issue in WordPress Environment’ is closed to new replies.