Skip to content

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

Closed
miss-islington wants to merge 1 commit intopython:3.13from
miss-islington:backport-706fd4e-3.13
Closed

[3.13] gh-142183: Cache one datachunk per tstate to prevent alloc/dealloc thrashing (GH-145789)#145829
miss-islington wants to merge 1 commit intopython:3.13from
miss-islington:backport-706fd4e-3.13

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>
@Yhg1s
Copy link
Member

Yhg1s commented Mar 11, 2026

(Replacing this with a backport of the 3.14 version.)

@Yhg1s Yhg1s closed this Mar 11, 2026
@miss-islington miss-islington deleted the backport-706fd4e-3.13 branch March 11, 2026 16:03
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants