You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Since Python 3.12 it is possible to profile Python programs using Linux perf profiler when setting PYTHONPERFSUPPORT=1 environment variable. Unfortunately currently built Python containers are missing fno-omit-frame-pointer -mno-omit-leaf-frame-pointer CFLAGS which result in quite useless perf stack traces. It would be great to have those extra CFLAGS added to the image build. That would allow everyone to do low overhead performance profiling on production systems.
Are there downsides to changing these by default? Presumably these are omitted by default in the compiler intentionally, and I'd like to make sure we understand why before we disable them (that upstream Python page is great, but the way I read it is "if you want perf, you should build this way" not necessarily "it's generally a good idea to build all Python binaries this way" which is a slightly different thing).
After typing that, I read your other links (thank you!!) and both Ubuntu and Fedora doing this by default for the whole distro is a pretty strong signal for me. 😄
Since Python 3.12 it is possible to profile Python programs using Linux perf profiler when setting PYTHONPERFSUPPORT=1 environment variable. Unfortunately currently built Python containers are missing
fno-omit-frame-pointer -mno-omit-leaf-frame-pointer
CFLAGS which result in quite useless perf stack traces. It would be great to have those extra CFLAGS added to the image build. That would allow everyone to do low overhead performance profiling on production systems.The text was updated successfully, but these errors were encountered: