Spitfire 0.66.0 release notes
Released: 2026-11-01
- Warm-up: set Options → Warm-up in the test editor (options.warmup, e.g. 1m) and thresholds and performance budgets are judged on the requests after it only; the slow first minutes while JIT, caches and connection pools fill no longer spoil the result. While the run warms up the live page shows its thresholds as "warming up".
- A new card on the run page, the HTML/PDF report and the summary CSV give after warm-up and the whole run side by side (p95, p99, error rate and Apdex from those seconds' own requests); the charts shade the warm-up. Example: 10 min with a 1m warm-up → thresholds look at the last 9 minutes.
- Stage table: with Ramping VUs and Ramping arrival rate each stage's target and the measured VUs, requests/s, p95 and error rate; the charts mark stage boundaries with dashed lines. Docs: Load model → Warm-up and How the math works → 9.
- Retention on time: per-second data now goes on the day it runs out, not when its whole month has (it used to stay up to 31 days longer). When the cut falls in the middle of a run only its older seconds go, its summary and report stay, and the run page says so. The Data retention card shows the date of the oldest per-second data.
Updating
Your installation tells you about a new release itself: admins see its notes and the update command for that installation at the top of the UI. The command backs up the database first and keeps the settings (Updating). You can also follow new releases with the RSS feed.