Skip to content

[3.14] gh-142183: Cache one datachunk per tstate to prevent alloc/dealloc thrashing (GH-145789)#145828

Open
miss-islington wants to merge 2 commits intopython:3.14from
miss-islington:backport-706fd4e-3.14
Open

[3.14] gh-142183: Cache one datachunk per tstate to prevent alloc/dealloc thrashing (GH-145789)#145828
miss-islington wants to merge 2 commits intopython:3.14from
miss-islington:backport-706fd4e-3.14

Conversation

@miss-islington
Copy link
Contributor

@miss-islington miss-islington commented Mar 11, 2026

Cache one datachunk per tstate to prevent alloc/dealloc thrashing when repeatedly hitting the same call depth at exactly the wrong boundary.


(cherry picked from commit 706fd4e)

Co-authored-by: T. Wouters thomas@python.org
Co-authored-by: blurb-it[bot] <43283697+blurb-it[bot]@users.noreply.github.com>

…loc thrashing (pythonGH-145789)

Cache one datachunk per tstate to prevent alloc/dealloc thrashing when repeatedly hitting the same call depth at exactly the wrong boundary.

---------
(cherry picked from commit 706fd4e)

Co-authored-by: T. Wouters <thomas@python.org>
Co-authored-by: blurb-it[bot] <43283697+blurb-it[bot]@users.noreply.github.com>
… of the

struct's layout. (The struct is only created by the runtime, and the new
field only used by the runtime, so it should be safe.)
@Yhg1s Yhg1s added the needs backport to 3.13 bugs and security fixes label Mar 11, 2026
@Yhg1s
Copy link
Member

Yhg1s commented Mar 11, 2026

@hugovk What do you think, is fixing a pathological performance degradation worth the risk of this change?

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants