Headline production metrics across the platform's upgrade arc — Drupal 8 (PHP 7.4) → Drupal 9 (PHP 8) → Drupal 10. Switch the range to see the last 7 days, month-by-month, or the full history since the migration began.
App Spectre_5 (live)Source New Relic APMData as of —Refresh daily (scheduled routine)
Last full day
Most recent complete day vs the day before.
Interpretation · updated daily by Claude
Automated read of the latest data — bottom line, phase comparison, and notable trends.
Bottom line — Drupal 11 is now the fastest and cleanest phase on record: 593ms average response, the lowest error rate (0.27%) of any phase, and an Apdex of 0.77 on a mature sample of ~7.0M requests collected over roughly seven weeks since the Aug 1 cutover. Overall traffic and error rates continue their long-run downward trend from the D8/D9 era, and the last 24 hours and 7 days show no error-rate anomalies of note.
D11 vs. baselines: response time improved 12% versus D10 (663ms) and 13% versus the D8 baseline (679ms); error rate roughly halved versus D8 (0.39%) and D9 (0.42%) and is meaningfully lower than D10 (0.36%). Apdex (0.77) sits essentially level with D9 and just 0.01 below D10 — no regression there.
Sample size note: the D11 phase is no longer "thin" — at ~7.0M requests over ~7 weeks it's now comparable in scale to D9 and larger than D10's own window, so this read is reasonably solid, not a small early sample.
Recent hourly anomaly: the 24h series shows a sharp latency/Apdex dip at 02:06 CT (resp spiked to 1598ms, Apdex fell to 0.51) with low traffic (1,327 reqs) at that hour; it recovered by the next hourly bucket and no elevated error rate accompanied it, consistent with an isolated slow-query or cold-cache blip rather than a sustained issue.
7-day trend: daily error rates have been trending down through the week (0.30% → 0.01% most recent day), with response time holding in the 460–620ms band; no day stands out as anomalous.
Maintenance window: the 2026-08-01 05:00–07:00 CT deploy/maintenance window is excluded from both the D10 and D11 phase aggregates, so neither version is penalized for the outage. That window is now well outside the current 24h/7d lookback ranges, so it doesn't appear in those series; it is visible as a traffic and Apdex dip in the weekly "full" series (the Aug 04 week bucket shows Apdex easing to 0.74 as the post-cutover cache warmed back up).
By release phase
Full-period averages per production version. Change vs the Drupal 8 baseline.
Performance over time
Response time, error rate and Apdex for the selected range.
Average response time
—
milliseconds · lower is better
Drupal 8Drupal 9Drupal 10dashed = version cutover
Error rate
% of requests
Apdex
target 0.5 s
Period
Resp (ms)
Apdex
Error %
Requests
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.
Spectre LMS · Production performanceServer-side New Relic APM aggregates.