Title: Add additional GC related benchmark · Issue #437 · python/pyperformance · GitHub
Open Graph Title: Add additional GC related benchmark · Issue #437 · python/pyperformance
X Title: Add additional GC related benchmark · Issue #437 · python/pyperformance
Description: Given this performance regression in Python 3.14, it would be nice if we had a benchmark which would have more clearly shown it before final release. I have a new GC specific benchmark but it doesn't do things that would show this regres...
Open Graph Description: Given this performance regression in Python 3.14, it would be nice if we had a benchmark which would have more clearly shown it before final release. I have a new GC specific benchmark but it doesn...
X Description: Given this performance regression in Python 3.14, it would be nice if we had a benchmark which would have more clearly shown it before final release. I have a new GC specific benchmark but it doesn...
Opengraph URL: https://github.com/python/pyperformance/issues/437
X: @github
Domain: github.com
{"@context":"https://schema.org","@type":"DiscussionForumPosting","headline":"Add additional GC related benchmark","articleBody":"Given this [performance regression in Python 3.14](https://github.com/python/cpython/issues/139951), it would be nice if we had a benchmark which would have more clearly shown it before final release. I have a [new GC specific benchmark](https://github.com/python/pyperformance/pull/381) but it doesn't do things that would show this regression.\n\nWe should consider adding a new benchmark. The key features would be:\n- creating a bunch of net new container objects, in order to trigger many, potentially young generation, collections\n- creating tuple objects that can be untracked by the GC, in order to avoid slowing down full collections\n\nIdeally we prefer to avoid a micro or synthetic benchmark and instead find some kind of real application that shows this regression. E.g. near the 3.13 release, we found a GC regression shown by Sphinx building Python docs. Something like that would be good.\n\n","author":{"url":"https://github.com/nascheme","@type":"Person","name":"nascheme"},"datePublished":"2025-10-28T18:20:04.000Z","interactionStatistic":{"@type":"InteractionCounter","interactionType":"https://schema.org/CommentAction","userInteractionCount":4},"url":"https://github.com/437/pyperformance/issues/437"}
| route-pattern | /_view_fragments/issues/show/:user_id/:repository/:id/issue_layout(.:format) |
| route-controller | voltron_issues_fragments |
| route-action | issue_layout |
| fetch-nonce | v2:f584ebc0-9617-e5e4-45e9-f5a4e2a66b4b |
| current-catalog-service-hash | 81bb79d38c15960b92d99bca9288a9108c7a47b18f2423d0f6438c5b7bcd2114 |
| request-id | C21A:33C049:D11957:11DBC05:6969EE16 |
| html-safe-nonce | 99bdae66342990bdeaa12027deb092b8f03a8c1f63124408bb5d5e3895079ec5 |
| visitor-payload | eyJyZWZlcnJlciI6IiIsInJlcXVlc3RfaWQiOiJDMjFBOjMzQzA0OTpEMTE5NTc6MTFEQkMwNTo2OTY5RUUxNiIsInZpc2l0b3JfaWQiOiIyMzQ3Mjg2NDA4ODQ2NzY1NTkwIiwicmVnaW9uX2VkZ2UiOiJpYWQiLCJyZWdpb25fcmVuZGVyIjoiaWFkIn0= |
| visitor-hmac | 78daa19e038d643d3762fded8e6c2d2ff3307731a4a0aa130bbcc3b74f31e9d4 |
| hovercard-subject-tag | issue:3562818646 |
| github-keyboard-shortcuts | repository,issues,copilot |
| google-site-verification | Apib7-x98H0j5cPqHWwSMm6dNU4GmODRoqxLiDzdx9I |
| octolytics-url | https://collector.github.com/github/collect |
| analytics-location | / |
| fb:app_id | 1401488693436528 |
| apple-itunes-app | app-id=1477376905, app-argument=https://github.com/_view_fragments/issues/show/python/pyperformance/437/issue_layout |
| twitter:image | https://opengraph.githubassets.com/699ea02626c0b68674e4ac74594d22941ef76fb44cefa75eb74625fa89d62b01/python/pyperformance/issues/437 |
| twitter:card | summary_large_image |
| og:image | https://opengraph.githubassets.com/699ea02626c0b68674e4ac74594d22941ef76fb44cefa75eb74625fa89d62b01/python/pyperformance/issues/437 |
| og:image:alt | Given this performance regression in Python 3.14, it would be nice if we had a benchmark which would have more clearly shown it before final release. I have a new GC specific benchmark but it doesn... |
| og:image:width | 1200 |
| og:image:height | 600 |
| og:site_name | GitHub |
| og:type | object |
| og:author:username | nascheme |
| hostname | github.com |
| expected-hostname | github.com |
| None | 7b32f1c7c4549428ee399213e8345494fc55b5637195d3fc5f493657579235e8 |
| turbo-cache-control | no-preview |
| go-import | github.com/python/pyperformance git https://github.com/python/pyperformance.git |
| octolytics-dimension-user_id | 1525981 |
| octolytics-dimension-user_login | python |
| octolytics-dimension-repository_id | 65949828 |
| octolytics-dimension-repository_nwo | python/pyperformance |
| octolytics-dimension-repository_public | true |
| octolytics-dimension-repository_is_fork | false |
| octolytics-dimension-repository_network_root_id | 65949828 |
| octolytics-dimension-repository_network_root_nwo | python/pyperformance |
| turbo-body-classes | logged-out env-production page-responsive |
| disable-turbo | false |
| browser-stats-url | https://api.github.com/_private/browser/stats |
| browser-errors-url | https://api.github.com/_private/browser/errors |
| release | bdde15ad1b403e23b08bbd89b53fbe6bdf688cad |
| ui-target | full |
| theme-color | #1e2327 |
| color-scheme | light dark |
Links:
Viewport: width=device-width