--load: notification fan-out load (resources/subscribe across many sessions)

未关闭
  • 哪里不对？
#2,913 1 条评论 0 个 reaction 已指派 0 人 在 GitHub 查看

维护者通常 1 天内回复

还没有人认领这个 Issue。

评估

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

调研方向

Start by reading the --load and --load-connections implementations to understand request timing and multi-connection handling; the issue does not name file paths. Then trace how resources/subscribe and notification delivery are represented, and decide how to measure subscribe cost, per-subscriber latency, and missed notifications across sessions. Done means a fan-out load mode reports those measurements for many sessions.

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

描述

enhancement v2
The problem

--load measures request/response latency only. A server's cost of fanning out notifications/resources/updated (or other notifications) to many subscribers, and the delivery latency each subscriber sees, is not measured.

Proposal

A fan-out mode: open N sessions, resources/subscribe each to a URI, then trigger updates (or wait for the server's own) and report per-notification delivery latency (from the trigger, or from the first subscriber's receipt), missed notifications per session, and the subscribe cost. It builds on the multi-connection machinery from --load-connections.

Split out of #2838 (item 9, "further ideas"), which covered items 1–8. Filed as follow-up work rather than built there, at the maintainer's request.

主要语言
TypeScript
星标
11.2k
派生
1.6k
平均合并
3 小时 52 分钟
30 天内合并 PR
142

环境准备

从这里开始

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

modelcontextprotocol/inspector 的其他 Issue

查看 modelcontextprotocol/inspector 的全部 Issue

相似的 Issue

更多 TypeScript Issue

把新 issue 发到你的邮箱

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