DeepSeek Harness Plugin Hub

发布与管理完整 Harness Profiles,发现适合你的插件。

探索

插件目录环境预设文档中心动态

社区

发布插件联系我们报告问题

相关链接

Plugin Hub GitHubDeepSeek Harness 官方项目系统状态隐私说明
© 2026 DeepSeek Harness Plugin HubPowered byPaxTech

独立、非官方社区项目,与 DeepSeek 官方无隶属、授权或背书关系。

Llm Latency — DeepSeek Harness 插件(DSH Plugin)
DeepSeek Harness Plugin Hub
ProfilesPlugins分类动态文档登录管理 Profiles
ProfilesPlugins分类动态文档登录
← Plugins
L

dsh-llm-latency

Llm Latency

用于 DeepSeek Harness 的按供应商/模型划分的大语言模型延迟遥测和跨供应商基准测试插件

插件会安装到这里;不确定时保持 web。

npx -y @deepseek-ai/dsh plugin --profile web add github:shengbinxu/dsh-llm-latency#535a3d0d4b4845a981478b3da151962c53c1a190
README兼容性版本
OverviewTime-window comparisonSession comparisonRequest log

兼容性与来源证明

Llm Latency 以 dsh-llm-latency 发布,当前版本为 0.1.0。Plugin Hub 会校验它的 manifest,并保存精确安装来源,便于复现安装结果。

DSH 兼容范围
*
运行环境
any
发布来源
github
Registry 更新时间
2026/8/29

版本

0.1.0stable
2026/8/29

相关插件

正在加载相关插件…

最新版
0.1.0
DSH
*
HMR
重启进程
Tree shaking
未声明可安全裁剪
解包体积
未提供
文件数
未提供
Surface
any
许可证
MIT
发布源
github
GitHub
★ 0
周下载
0
最近提交
2026/8/29
查看源码 ↗
README Badge

点击下方 Badge 复制 Markdown,粘贴到 README 即可。

这是你的 Plugin?认领权益 · 优先安全扫描

验证 package.json 声明的 GitHub 仓库,即可管理这个公开页面。认领后,Hub 会优先安排当前版本的安全扫描,并在通过后公开展示结果。

认领这个 Plugin →
报告问题

相关插件

继续浏览 models-usage 分类下经过校验的插件。

Usage@linxin666/dsh-usagedsh Web GUI 的使用统计插件:检测各提供商余额和编码计划配额,并提供实时令牌使用记录,以及当前提供商的专属宠物气泡Whale Widgetdsh-whale-widgetDSH Web 界面右下角的 DeepSeek 余额小鲸鱼挂件:余额/今日已用/峰谷定价、自定义泡泡点击序列(文本/余额/今日/峰谷/图片/随机语句与并列加权选择)、逐行样式与字体、悬浮快捷编辑、音效与每轮消耗、自定义角色/动图/音效、吸附与翻转自定义Usage Stats@ychris12138/dsh-usage-statsdsh Web GUI 的令牌使用热力图、提供商余额和订阅配额Codex Connectdsh-codex-connect用于 DeepSeek Harness 的 ChatGPT OAuth 和 Codex 模型。

README

dsh-llm-latency

English · 中文

Per-vendor / per-model / per-session LLM latency and cache-hit telemetry for DeepSeek Harness. It answers with numbers: "which vendor is actually faster, and whose cache hits better — for the same model, over the same period?"

  • Passive telemetry — every real model call is measured (first token, end-to-end, tokens/sec, cache-hit share) and classified by failure kind (429 / timeout / 5xx / abort).
  • Three comparisons:
    1. Overview — rank all vendor·model rows over any time window.
    2. Time-window — same model across vendors over an arbitrary window (e.g. today 10:00–10:30), with P50/P90/P95/P99, failure rates, cache-hit rate, sample counts, and median significance.
    3. Session — run the same prompt in two sessions, each pinned to one vendor's model, then compare the whole runs; valid only when a session never switched models.
  • Dashboard + tool — a self-contained HTML dashboard (overview / time-window / session / request-log views) plus the latency_report model tool and CSV export.
  • Request log — every model call is persisted as one record (time, vendor, model, session, request id, credential ref, TTFT, end-to-end, input/output tokens, cache-hit rate, status), searchable and filterable in the dashboard.

See DESIGN.md for the data model and comparison methodology.

Screenshots

Overview — rank every vendor·model row over a time window.

Overview

Time-window — the same model across vendors, with P50/P90/P95/P99, failure rates, cache-hit rate, and median significance.

Time-window comparison

Session — compare two single-model sessions side by side.

Session comparison

Request log — search and filter every model call.

Request log

Install

dsh plugin --profile web add github:shengbinxu/dsh-llm-latency

Then restart the profile. The plugin applies after dsh-base (it needs the llm service), intercepts llm/stream, and serves the dashboard at:

http://127.0.0.1:3080/llm-latency/

Usage

  • Dashboard — switch between 总览 / 时段对比 / 会话对比 / 请求日志:
    • 时段对比: pick a model, pick a window, compare vendors side by side.
    • 会话对比: pick two sessions that each used a single model, compare them.
    • 请求日志: search and filter every model call by request id, vendor, model, session, credential ref, or status.
  • Model tool — ask the agent "帮我看看各厂商延迟对比" (latency_report); it accepts model, vendors, from/to, and sessionIds.

Where data lives

Aggregates persist at $DSH_HOME/llm-latency/stats.json (default ~/.dsh/llm-latency/stats.json). Delete the file to reset. The request log is append-only at $DSH_HOME/llm-latency/requests.jsonl.

Metrics

  • TTFT (primary) — time to first content chunk; e2e — full stream; tok/s — decode throughput.
  • Cache-hit rate — cacheRead / (input + cacheRead + cacheWrite); cache-write rate — cacheWrite / (input + cacheRead + cacheWrite).
  • Failure breakdown — 429 (rate-limited), timeout, 5xx, abort, other, each as a share of attempts. Retries are separate llm/stream calls, so a 429 is recorded as an attempt-level failure.

Comparison methodology

Same-model cross-vendor comparisons always slice every vendor to the same time window. Percentiles come from merged histograms; the median's 95% bootstrap confidence interval comes from the recent sample ring when the window has enough samples (minSamplesForComparison). Two vendors differ significantly when their median CIs do not overlap. Insufficient samples and gross sample imbalance are flagged.

Configuration

Set in cordis.patch.yml (or override the row):

KeyDefaultMeaning
retentionDays30Data retention window in days
recentLimit2000Per-key exact-sample ring cap
sessionLimit500Sessions retained (most recent first)
spikeFloorMs10000TTFT above this counts as a spike
modelAliases{}Canonical model → provider model ids
minSamplesForComparison20Minimum ok samples before a median CI is reported
logLimit5000Request-log mirror cap (recent records kept)
logRetentionDays7Request-log retention window in days

How it works

The plugin registers a waterfall listener on llm/stream, wraps the returned AsyncIterable<StreamChunk>, and starts its clock on the first pull — the moment the adapter lazily issues the HTTP request. Failures carry the harness LlmFailure.code/.status, mapped to the five-class taxonomy above.

License

MIT