Inference engine startup included in GPU metric capture / 推理引擎启动阶段被纳入 GPU 指标采集

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

维护者通常 1 天内回复

@arygupt 已经在做这个了。

开始于 2026年5月22日。

评估

这个 Issue 还没有评估数据。

描述

Describe the bug
Current scripts in the benchmarks/single_node directory (e.g., https://github.com/SemiAnalysisAI/InferenceX/blob/adbaae52ddf2569ddf2e793f5ad0a56f2f2a4d13/benchmarks/single_node/qwen3.5_fp8_mi325x.sh) follow this pattern to establish GPU monitoring for every InferenceX benchmark run:

  1. start_gpu_monitor
  2. Start LLM inference engine as a background process (e.g. SGLang, vLLM)
  3. wait_for_server_ready
  4. Run benchmark for the model (key result to report for InferenceX benchmark)
  5. stop_gpu_monitor

As-is, the GPU energy consumption and other metrics can be skewed by irregularities in LLM inference engine startup (compilation, kernel autotuning, etc) and the 5-second sleeps used while waiting for the server to start (waiting on the /health route). While cross-referencing other logs can identify some timestamps that fall outside of the actual benchmark window, there is no direct correspondence within the CSV itself.

Expected behavior
Monitoring data should only correspond to the benchmark execution window. Alternatively, providing a way to identify which portion of the data corresponds to benchmark execution would also be acceptable.

Potential solutions
Adding a marker in the gpu_metrics.csv or delaying the start_gpu_monitor calls until the benchmark is ready to run (moving step 1 above to just before step 4) can assist in disambiguating the results.

Additional context
The startup costs of pinned versions of vLLM (likely similar for other engines) should be relatively consistent for a GitHub action runner, but the inference engine's startup performance can change over successive versions. The ability to separate startup costs from the benchmark data is important.

中文说明

当前基准测试脚本在推理引擎启动之前就开始 GPU 监控（start_gpu_monitor），导致 gpu_metrics.csv 中包含引擎启动阶段（编译、内核自动调优、等待 /health 路由的休眠等）的能耗和指标数据，这会影响基准测试指标的准确性。建议将 GPU 监控延迟到基准测试实际运行前启动，或在 CSV 中添加标记以区分启动阶段和基准测试执行窗口的数据。

主要语言
Python
星标
2k
派生
354
平均合并
2 天 40 分钟
30 天内合并 PR
431

环境准备

从这里开始

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

SemiAnalysisAI/InferenceX 的其他 Issue

查看 SemiAnalysisAI/InferenceX 的全部 Issue

相似的 Issue

更多 Python Issue

把新 issue 发到你的邮箱

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