feature: add burst pacing mode and --duration flag (v0.14.1)#150
Merged
Conversation
- mode: burst fires requests at full worker concurrency with no inter-request delay; intended for internal infrastructure and load experiments only - pacing.ramp_up_s: optional linear ramp-up — inter-request delay decreases from ~50ms × remaining_ramp_up_s to zero, preventing a cold-start spike - --duration flag on sendit start: auto-stops after a wall-clock time; required when mode is burst (safety gate — no unbounded burst sessions) - Config validation accepts burst mode, skips rpm check for burst - Dry-run output shows burst config with internal-use reminder - Scheduler tests: NoRampUp, RampUp, ContextCancel, SteadyStateAfterRampUp - startCmd tests: DurationFlag registered, BurstRequiresDuration error - Config test: burst is now valid; aggressive is still invalid - Docs: burst mode section in pacing.md; --duration in cli.md Co-Authored-By: Claude Sonnet 4.6 <noreply@anthropic.com>
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Summary
mode: burst— new pacing mode that fires requests at full worker concurrency with no inter-request delay; intended for internal infrastructure testing and load experiments against services you ownpacing.ramp_up_s— optional linear ramp-up: inter-request delay decreases from50ms × remaining_ramp_up_sto zero over the ramp window, preventing a cold-start spike against the target--duration <duration>onsendit start— auto-stops the engine after a wall-clock time (e.g.--duration 5m); triggers the same graceful shutdown as SIGTERM; required whenpacing.modeisburst— no unbounded burst sessionsburstand skips therequests_per_minute > 0check (unused in burst mode)--durationworks for any pacing mode (optional for human/rate_limited/scheduled, required for burst)Test plan
TestScheduler_Burst_NoRampUp— burst with no ramp-up returns immediatelyTestScheduler_Burst_RampUp— first call delayed; post-ramp calls immediateTestScheduler_Burst_ContextCancel— cancels cleanly during ramp-up sleepTestScheduler_Burst_SteadyStateAfterRampUp— immediate after ramp-up expiresTestStartCmd_BurstRequiresDuration— error when burst mode without--durationTestStartCmd_DurationFlag— flag registered on startCmdmode: burstvalid;mode: aggressivestill invalid🤖 Generated with Claude Code