Hacktoberfest 2026:维护者为十月标记出来的 issue,仍然开放、适合新手。 浏览 Hacktoberfest issue

--load: ramp-up and stepped load to find a server's knee

未关闭
#2,841 1 条评论 0 个 reaction 已指派 0 人 在 GitHub 查看

维护者通常 1 天内回复

还没有人认领这个 Issue。

评估

难度
5/5
预计耗时
一周以上
新手友好度
35/100
Issue 类型
功能
描述清晰度
基本清楚
活跃度
活跃
技术栈
typescript

调研方向

Start by locating the shared core code that handles --load-concurrency and produces JSON summaries; the issue does not name files or tests. Compare how concurrency and rate are configured, then determine how ramp or step runs could produce one summary row per step. Done means the requested load progression and optional threshold stop are specified and covered by tests.

由索引模型根据 Issue 内容生成。

描述

enhancement v2
Which client?

All / shared core

The problem

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.
主要语言
TypeScript
星标
11.2k
派生
1.6k
平均合并
5 小时 11 分钟
30 天内合并 PR
141

环境准备

从这里开始

  1. 先读完整个 Issue,再读项目的贡献指南。
  2. 在 Issue 下留言说明你要接手 —— 这能避免两个人做同样的事。
  3. Fork 仓库,在一个分支上完成修改。
  4. 提交 Pull Request,并在描述里引用这个 Issue 编号。

modelcontextprotocol/inspector 的其他 Issue

查看 modelcontextprotocol/inspector 的全部 Issue

相似的 Issue

更多 TypeScript Issue

把新 issue 发到你的邮箱

精选适合新手参与的 GitHub issue 摘要。