Prerequisites
Description
When running Locust at very high request rates (10k+ RPS), storing every single request in memory for stats becomes expensive and can affect test accuracy. Users need a way to sample requests - for example, only record 1 out of every 100 requests for statistics while still sending all traffic. This would keep the load realistic while reducing memory pressure and stats processing overhead. Sampling rate should be configurable per test run, and sampled vs non-sampled requests should be clearly marked in any exported data.
Prerequisites
Description
When running Locust at very high request rates (10k+ RPS), storing every single request in memory for stats becomes expensive and can affect test accuracy. Users need a way to sample requests - for example, only record 1 out of every 100 requests for statistics while still sending all traffic. This would keep the load realistic while reducing memory pressure and stats processing overhead. Sampling rate should be configurable per test run, and sampled vs non-sampled requests should be clearly marked in any exported data.