Add additional GC related benchmark
还没有人认领这个 Issue。
- 主要语言
- Python
- 星标
- 1k
- 派生
- 203
- 平均合并
- 1 小时 20 分钟
- 30 天内合并 PR
- 2
描述
Given this performance regression in Python 3.14, it would be nice if we had a benchmark which would have more clearly shown it before final release. I have a new GC specific benchmark but it doesn't do things that would show this regression.
We should consider adding a new benchmark. The key features would be:
- creating a bunch of net new container objects, in order to trigger many, potentially young generation, collections
- creating tuple objects that can be untracked by the GC, in order to avoid slowing down full collections
Ideally we prefer to avoid a micro or synthetic benchmark and instead find some kind of real application that shows this regression. E.g. near the 3.13 release, we found a GC regression shown by Sphinx building Python docs. Something like that would be good.
贡献指南
这个仓库没有索引到贡献指南
从这里开始
- 先读完整个 Issue,再读项目的贡献指南。
- 在 Issue 下留言说明你要接手 —— 这能避免两个人做同样的事。
- Fork 仓库,在一个分支上完成修改。
- 提交 Pull Request,并在描述里引用这个 Issue 编号。
调研方向
首先阅读链接的 Python 3.14 性能回归问题,以及 pull request 381 中现有的 GC 专用基准测试。调查一个真实应用基准,而不是合成微基准;该基准应创建大量新的容器对象和不可跟踪的元组,并暴露这一回归;完成标准是在发布前,基准测试能够清楚地显示这一行为。
由索引模型根据 Issue 内容生成。
评估
- 技术栈
- python
- 领域
- performance
- Issue 类型
- 功能
- 难度
- 5/5
- 预计耗时
- 一周以上
- 活跃度
- 停滞
- 描述清晰度
- 需要澄清
- 新手友好度
- 35/100