Spitfire 0.65.0 release notes
Released: 2026-11-01
- Pacing: in the VU-based load models (Constant VUs, Ramping VUs, the iteration models) Load model → Pacing starts each VU's iteration at a fixed interval (e.g. 30s) or a random one (min–max); when an iteration is quick the VU waits out the rest. Example: 100 VUs every 30 s → ≈3.3 iterations/s; the plan line shows the rate.
- When an iteration takes longer than the interval the next starts at once, the new pacing_missed counter goes up and missed starts are not made up in a burst; above 0.1% missed the report shows a finding, and it works as a threshold (pacing_missed count<1). VUs' first iterations are staggered by default.
- The license check counts the paced rate in the peak requests/s; a Constant Throughput Timer under a JMeter thread group becomes pacing on import. Docs: Load model → Pacing and How the math works → 8.
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.