Drupal Migration — Performance Monitor

Bottom line — Spectre_5 is healthy over the last 24 hours (390–710ms response outside the overnight window, apdex mostly 0.71–0.86), with the only notable disruption being the planned Aug 1 maintenance window rather than any new instability. The Drupal 11 upgrade's first ~57 hours of live traffic show response times and error rates running slightly better than both the Drupal 10 and Drupal 8 baselines, though the sample is still small and should be read as an early, provisional signal rather than a settled trend.

• D11 early read: Drupal 11 is averaging 604ms response / 0.29% errors / 0.77 apdex on ~140K requests since going live — faster and cleaner than Drupal 10 (664ms / 0.36% / 0.78 apdex) and Drupal 8 (679ms / 0.39% / 0.79 apdex), but the request volume is a small fraction of the multi-million-request D8/D9/D10 samples, so this should firm up over the next 1–2 weeks before drawing conclusions.
• Maintenance window visible in the raw series: the Aug 1 05:00–07:00 Chicago deploy window is excluded from the D10/D11 phase aggregates, but it still shows up as a clear traffic dip in the daily view — Aug 1 request volume (~41.8K) is roughly a third of the surrounding days (~150K), with Aug 2 still recovering (~89K) as caches warmed back up.
• Overnight anomaly in the last 24h: a brief error spike to 8.12% at 01:08 and a latency/apdex dip (1386ms, apdex 0.58) at 03:08 stand out against an otherwise stable low-traffic overnight period; both were isolated single-hour buckets with no lasting effect on the following hours.
• Daytime performance stable: across the current 24h peak-traffic hours (06:08–10:08), response time held in the 610–710ms band with apdex 0.74–0.79 and error rates under 0.55%, consistent with typical peak-load behavior seen in prior weeks.
• Weekly trend unremarkable pre-maintenance: excluding the Aug 1–2 dip, the trailing 7 days show response time drifting narrowly between 609–683ms with error rates under 0.4%, indicating no pre-existing degradation ahead of the D11 cutover.

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.