Improve performance of inherited mapping assignment slot calls
還沒有人認領這個 Issue。
- 主要語言
- Python
- 星號
- 77.2k
- 分支
- 36k
- 平均合併
- 1 天 9 小時
- 30 天內合併 PR
- 558
描述
Feature or enhancement
Proposal:
__setitem__ and __delitem__ share the mp_ass_subscript slot. If a Python subclass of a C mapping overrides only one of them, slot_mp_ass_subscript() is used for both operations.
For example, collections.Counter overrides __delitem__ but inherits dict.__setitem__. Assigning an item looks up the inherited wrapper_descriptor and calls it through the generic tp_call path. Since PyWrapperDescr_Type does not support vectorcall, _PyObject_MakeTpCall() and wrapperdescr_call() each create a temporary argument tuple before reaching dict's C slot.
Reproducer:
from collections import Counter
from time import perf_counter_ns
obj = Counter()
start = perf_counter_ns()
for index in range(20_000_000):
obj[0] = index
print((perf_counter_ns() - start) / 1_000_000)
On macOS 15.7.1 arm64 with a release build of main (d856402e7176e5a03c5c578f0efc1be968be3257), using two warmups and nine alternating-order samples:
main: 1402.07 ms median (1376.93–1445.12 ms)
prototype: 859.97 ms median (846.24–902.74 ms)
The prototype calls the inherited C slot directly when lookup returns the expected unbound mapping slot wrapper, and otherwise keeps the existing call path. This reduced the benchmark time by 38.66%.
The relevant call-path files are unchanged at b062727097e997bcb900e11503d3248daac903da.
Has this already been discussed elsewhere?
This is a minor feature, which does not need previous discussion elsewhere
Links to previous discussion of this feature:
No response
Linked PRs
- gh-156258
貢獻指南
從這裡開始
- 先讀完整個 Issue,再讀專案的貢獻指南。
- 在 Issue 下留言說明你要接手 —— 這能避免兩個人做同樣的事。
- Fork 儲存庫,在一個分支上完成修改。
- 送出 Pull Request,並在描述裡引用這個 Issue 編號。
研究方向
先閱讀 issue 中描述的 slot_mp_ass_subscript()、_PyObject_MakeTpCall() 和 wrapperdescr_call() 路徑,然後檢查連結的 PR gh-156258。完成的標準是,繼承的 mapping 指派路徑在保留現有 fallback 的同時避免暫時的引數 tuple,並且提供的 Counter 基準測試顯示出所報告的改善。
由索引模型根據 Issue 內容生成。
評估
- 技術堆疊
- python
- 領域
- performance
- Issue 類型
- 功能
- 難度
- 4/5
- 預估耗時
- 3-5 天
- 活躍度
- 停滯
- 描述清晰度
- 基本清楚
- 新手友好度
- 35/100