Improve the efficiency of trace stitching
未关闭
还没有人认领这个 Issue。
3.14
interpreter-core
performance
- 主要语言
- Python
- 星标
- 77.2k
- 派生
- 35.9k
- PR 合并指标
- PR 指标待抓取
描述
From the way benchmarks have been responding to recent PRs, it certainly seems like side exits could be made more efficient, especially in the happy path. This is especially true of _DYNAMIC_EXIT, which needs to do quite a bit of work for a successful stitch... perhaps the best option here is to just reduce the number of _DYNAMIC_EXITs that we run.
This could also include recompiling stitched traces together into the same executor to essentially remove stitching overhead, too.
Linked PRs
- gh-122295
贡献指南
从这里开始
- 先读完整个 Issue,再读项目的贡献指南。
- 在 Issue 下留言说明你要接手 —— 这能避免两个人做同样的事。
- Fork 仓库,在一个分支上完成修改。
- 提交 Pull Request,并在描述里引用这个 Issue 编号。
调研方向
该 issue 没有指定文件或测试。首先检查 benchmark 响应以及 _DYNAMIC_EXIT 附近的 trace-stitching 路径;确定减少 dynamic exits 或重新编译 stitched traces 是否可行。当能够证明相关 benchmark 上的 stitching 开销降低时,即视为完成。
由索引模型根据 Issue 内容生成。
评估
- 技术栈
- python
- 领域
- performance
- Issue 类型
- 重构
- 难度
- 5/5
- 预计耗时
- 一周以上
- 活跃度
- 停滞
- 描述清晰度
- 需要澄清
- 新手友好度
- 20/100