You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
Repository navigation
--load: ramp-up and stepped load to find a server's knee #2841
A fixed concurrency or rate shows how a server behaves at one load level. Finding where latency or errors start climbing (the knee) means many separate runs and stitching their summaries together by hand.
Solution you have in mind (optional)
--load-ramp <from>:<to>:<duration> (concurrency or rate) and/or --load-steps 10,25,50,100 --load-step-duration 30, with one summary row per step, and optionally stop at the first step that breaches a threshold.
Alternatives or workarounds you have tried
A shell loop over --load-concurrency values, parsing each JSON summary with jq.
Already built it locally?
No response
Before you submit
I searched existing issues and this is not a duplicate.
This is a request for the Inspector itself, not for the MCP specification or an SDK.
Activity
cliffhall commentedon Oct 29, 2026
Triage: Priority Low (total 4)
Board: #28, Status
Incoming(awaiting maintainer review — no milestone yet).cliffhall commentedon Nov 5, 2026
Shipped in #2909 (merge 219e605).