python / python/cpython

Avoid unnecessary NotShareableError creation in XIData FULL_FALLBACK

未關閉
#148,223 0 則留言 0 個 reaction 已指派 0 人 在 GitHub 檢視

還沒有人認領這個 Issue。

interpreter-core type-feature
主要語言
Python
星號
77.2k
分支
35.9k
PR 合併指標
PR 指標待擷取

描述

Proposal:
Motivation

The pickle fallback path in _PyObject_GetXIData() does unnecessary work on successful transfers of types that are not in the XIData registry, creating and discarding a NotShareableError that user code never sees.

This is a follow-up to gh-148072 / GH-148125, which cached pickle.dumps and pickle.loads per interpreter. That change removed module lookup overhead, but there is still avoidable cost in the fallback path itself.

This extra exception work adds measurable overhead to cross-interpreter transfers that rely on pickle fallback.

Approach

Check the XIData registry first with lookup_getdata() before calling _get_xidata().

  • If the type is registered, keep using the existing path unchanged.
  • If the type is not registered, skip _get_xidata() and go directly to the function/pickle fallback chain.

On total failure, raise the same NotShareableError as the existing code path, so external behavior stays the same.

Benchmark results

This removes unnecessary exception creation on a hot fallback path and gives a measurable speedup for transfers that rely on pickle fallback.

In local benchmarks on Apple M2, combined with GH-148125, this improved round-trip transfer times for mutable objects such as list and dict, especially for larger payloads.

Large-payload benchmark results (500 iterations, Apple M2)

Baseline is upstream/main after GH-148125 (pickle cache). "After" includes this change.

Data Before After Speedup
list [1 x 100KB] 1.19ms 0.12ms 9.9x
list [1 x 1MB] 10.26ms 0.20ms 51x
list [10 x 100KB] 9.99ms 0.10ms 100x
dict {10 x 100KB} 10.41ms 0.26ms 40x
Related
  • gh-148072 — Predecessor: pickle module caching (merged as GH-148125)
  • gh-124694 — InterpreterPoolExecutor addition
Validation

Local testing passed:

  • ./python -m test test_interpreters
  • ./python -m test test_concurrent_futures
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:
Linked PRs
  • gh-148224

貢獻指南

開啟貢獻指南

從這裡開始

  1. 先讀完整個 Issue,再讀專案的貢獻指南。
  2. 在 Issue 下留言說明你要接手 —— 這能避免兩個人做同樣的事。
  3. Fork 儲存庫,在一個分支上完成修改。
  4. 送出 Pull Request,並在描述裡引用這個 Issue 編號。

研究方向

_PyObject_GetXIData() 開始,追蹤 pickle fallback 路徑中的 lookup_getdata()_get_xidata()。查看關聯的 PR gh-148224,然後執行 ./python -m test test_interpreters./python -m test test_concurrent_futures;完成的標準是在保留現有 NotShareableError 行為的同時,避免不必要地建立例外。

由索引模型根據 Issue 內容生成。

評估

技術堆疊
python
領域
backend, performance
Issue 類型
重構
難度
4/5
預估耗時
3-5 天
活躍度
停滯
描述清晰度
基本清楚
新手友好度
25/100

把新 issue 寄到你的電子郵件信箱

精選適合新手參與的 GitHub issue 摘要。