Hacker News new | past | comments | ask | show | jobs | submit login

> 9X% of users do not care about a <1% drop in performance.

Except Python got opted out of the frame pointer change due to benchmarks showing slowdowns of up to 10%. The discussion around that had the great idea of just adding a pragma to flat out override the build setting. So in the end that "%1" reduction claim only holds if everything even remotely affected silently ignores the flag.






This is a bit of a mischaracterization of the Python side of things.

They only opted out for 3.11 which did not yet have the perf-integration fixes anyway. 3.12 uses frame-pointers just fine.


Any link to the fix or documentation about it? I could find added perf support but did not see anything about improved performance related to frame pointer use.

https://pagure.io/fesco/issue/2817#comment-826636 will probably get you started into the relevant paths. Python 3.12 was going to include frame-pointers anyway for perf to boot. So they needed to fix this regardless.



Guidelines | FAQ | Lists | API | Security | Legal | Apply to YC | Contact

Search: