NotificationsYou must be signed in to change notification settings
Fork32.1k
Star67.3k

[3.14] gh-132917: Use /proc/self/status for mem usage info. (GH-133544)#133718

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to ourterms of service andprivacy statement. We’ll occasionally send you account related emails.

Already on GitHub?Sign in to your account

Jump to bottom

Merged

nascheme merged 1 commit intopython:3.14frommiss-islington:backport-751db4e-3.14

May 8, 2025

Merged

[3.14] gh-132917: Use /proc/self/status for mem usage info. (GH-133544)#133718

nascheme merged 1 commit intopython:3.14frommiss-islington:backport-751db4e-3.14

May 8, 2025

Conversation

Copy link

Contributor

miss-islington commentedMay 8, 2025•
edited by bedevere-appbot
Loading

On Linux, use /proc/self/status for mem usage info. Using smaps_rollup is quite a lot slower and
we can get the similar info from /proc/self/status.
(cherry picked from commit751db4e)

Co-authored-by: Neil Schemenauernas-github@arctrix.com

Issue:GC performance regression in free threaded build #132917

pythongh-132917: Use /proc/self/status for mem usage info. (pythonGH-…

06a4884

…133544)On Linux, use /proc/self/status for mem usage info.  Using smaps_rollup is quite a lot slower andwe can get the similar info from /proc/self/status.(cherry picked from commit751db4e)Co-authored-by: Neil Schemenauer <nas-github@arctrix.com>