Drupal Migration — Performance Monitor

Bottom line — Drupal 11 is running faster and cleaner than every prior phase: average response time is down to 595 ms (vs. 663 ms on D10 and 679 ms on the D8 baseline) and the error rate has fallen to 0.25%, the lowest of the four phases. Apdex is essentially flat at 0.77, in line with D9/D10 and just a hair below D10's 0.78. With ~7.70M requests logged since the Aug 1 upgrade — already more volume than the D8 baseline and over twice D10's window — this is a solid production read, not a thin early sample.

• D11 vs. D10/D8: response time improved ~10% over D10 and ~12% over the D8 baseline, with the lowest error rate of any phase (0.25% vs. 0.36% on D10, 0.39% on D8). Apdex held steady rather than improving, so the win is in latency and reliability, not perceived responsiveness.
• 2026-08-01 maintenance window excluded from phase stats: the 05:00–07:00 Chicago deploy/maintenance window is not counted in the D10 or D11 aggregates, but it is still visible as a traffic dip in the 24h/7d time series for anyone reviewing that date range.
• 24h anomaly: a single overnight bucket (02:08 Chicago) spiked to 1156 ms average response with Apdex dropping to 0.59, well outside the otherwise tight 430–730 ms overnight band — worth a look if it recurs, though traffic in that bucket was low (~2.2K requests).
• 7-day trend: daily traffic climbed from ~29K to ~242K requests through the week with response time staying in a stable 527–634 ms range and error rates low (0–0.06%), no signs of degradation under increasing load.
• Longer-term (weekly) view: response times have hovered in the 520–700 ms band since the D11 cutover with no sustained regression; the most recent full weeks (Sep 11, Sep 18) show some of the lowest error rates in the past 13 months.

Method & caveats

• Cutovers. Drupal 9 / PHP 8 went live May 23, 2026; Drupal 10 Jul 4, 2026 — marked on every chart that spans them.
• Drupal 10 is an early read (~5 days). Its phase card uses the Jul 4–9 window directly.
• Recent spike. Jul 8 shows an isolated response jump (≈2× the prior day), coinciding with elevated reports/progress-API latency that day — an operational blip, not a migration regression.
• Source & retention. New Relic timeslice metrics (HttpDispatcher, Apdex, Errors/all), ~13-month retention — the full arc back to mid-2025 is covered. Percentiles (p95/p99) live in 8-day event data and are reported in the point-in-time reviews, not here.
• Refresh. Regenerated daily by a scheduled routine that re-queries New Relic and redeploys to this same URL.