WP Engine Server Performance Review — 2026-04-05

Overview

Vendor account review call between Mark Hope (Asymmetric) and Anthony Armendarez (WP Engine) to diagnose persistent CPU and PHP memory spikes on Asymmetric's shared WP Engine server. The account hosts ~40–48 small production WordPress sites, none exceeding ~1,000 visits/month. Despite low traffic across the board, a handful of installs are consuming a disproportionate share of server resources and generating thousands of 502/504 errors over the trailing 30 days.

The core finding: the problem is not traffic volume — it is inefficient code or plugin loops running on otherwise quiet sites. WP Engine will open engineering tickets for a deep-dive analysis and deliver findings and optimization recommendations by Friday, followed by a follow-up call with an engineer the week of the meeting.

Attendees:
- Anthony Armendarez — WP Engine (anthony.armendarez@wpengine.com)
- Mark Hope — Asymmetric (mark.hope@asymmetric.pro)

Key Decisions

• Engineering investigation confirmed for the three top offending installs: Village of Maple Bluff, Citrus America, and Scallon.
• Site Monitoring ruled out as the primary tool — per-site pricing is impractical across 40+ low-traffic sites.
• APM (Application Performance Monitoring) identified as the preferred proactive tool — flat $150/month per server, provides code-level alerts and actionable fix guidance rather than passive graphs.
• Follow-up call to be scheduled for Monday at the earliest, contingent on engineering completing their analysis.

Problem: Resource Hogs on Low-Traffic Sites

WP Engine's Insights dashboard and internal graphs show CPU and PHP memory usage nearing or exceeding plan limits on an hourly basis. A pie chart breakdown of server load by install reveals that ~60% of total server usage is concentrated in a small number of named installs:

Mark's framing: "If you take 1,000 visits a month and divide by 30 days, that's 33 visits a day. There should be nothing on this server causing us trouble."

Root Cause: Inefficient Plugin Loops

The working hypothesis — supported by a prior resolved incident — is that inefficient plugin behavior (query loops, excessive internal requests) is the driver, not traffic.

Precedent — Doodle of Farms:
A prior site on the same server was generating ~3,000 database queries per page load against a normal baseline of ~100. The culprit was identified via AI-assisted PHP log analysis (Claude Code). Disabling several WooCommerce and activity-logging plugins resolved the issue. The site no longer appears in WP Engine's problem list.

Current suspects follow the same pattern:
- Village of Maple Bluff: 72 organic visits/month generating 24% of all server requests — physically impossible without a loop or runaway process.
- Citrus America: Logging thousands of 502/504 errors despite being a low-volume site.
- Scallon: A stable 4–5 year old site that has recently become a top offender with no obvious change in traffic or content.

Mark's current workaround — manually pulling PHP files and analyzing them via ChatGPT — is unsustainable at scale.

Proposed Solution: APM Add-on

Anthony introduced WP Engine's Application Performance Monitoring (APM) add-on as the most appropriate tool for Asymmetric's situation.

• What it does: Server-level monitoring that provides code-level alerts and specific, actionable fix guidance — not just performance graphs.
• Cost: $150/month flat rate per server, regardless of plan size or number of installs.
• Why it fits: Asymmetric needs a single tool that covers all ~40 sites on one server. Per-site tools like Site Monitoring are cost-prohibitive at this scale and don't address the underlying code issues.
• Site Monitoring: Mark has one license included in his premium plan; Anthony will confirm status and advise on trials, but both agreed it is not the primary solution here.

"Just telling us that you've got a problem isn't particularly helpful. Tell us how to fix it." — Mark Hope

APM directly addresses this gap by surfacing what is causing the spike and what to do about it.

Action Items

Key Transcript Excerpts

On Village of Maple Bluff's resource usage being inexplicable:

"Their organic traffic is 72. And so there's no way they should be using up 24% of the requests for our entire server with 72 visits." — Mark Hope

On the Doodle of Farms precedent:

"We were in this crazy query loop where we were getting 3,000 queries on a site that should have 100. We turned off a couple of WooCommerce plugins and other things, and that helped. And it's not showing up in your screen anymore as a problem." — Mark Hope

On what Asymmetric actually needs from WP Engine:

"All these graphs that you guys are providing are really cool. But what would be even better would be to say, hey, you're having this problem, and here's what you need to do. Tell us how to fix it." — Mark Hope

On Scallon going off the rails unexpectedly:

"We've had this same site for four or five years, but all of a sudden it's a problem. And so what I've been doing is taking the PHP files and going to ChatGPT and saying, what's happening here? But surely there must be a better way to do that." — Mark Hope

Related

• ^[1]
• ^[2]