mirror of
https://github.com/NixOS/nixpkgs.git
synced 2024-12-25 23:23:07 +00:00
480c8d1991
I took a close look at how Debian builds the Python interpreter,
because I noticed it ran substantially faster than the one in nixpkgs
and I was curious why.
One thing that I found made a material difference in performance was
this pair of linker flags (passed to the compiler):
-Wl,-O1 -Wl,-Bsymbolic-functions
In other words, effectively the linker gets passed the flags:
-O1 -Bsymbolic-functions
Doing the same thing in nixpkgs turns out to make the interpreter
run about 6% faster, which is quite a big win for such an easy
change. So, let's apply it.
---
I had not known there was a `-O1` flag for the *linker*!
But indeed there is.
These flags are unrelated to "link-time optimization" (LTO), despite
the latter's name. LTO means doing classic compiler optimizations
on the actual code, at the linking step when it becomes possible to
do them with cross-object-file information. These two flags, by
contrast, cause the linker to make certain optimizations within the
scope of its job as the linker.
Documentation is here, though sparse:
https://sourceware.org/binutils/docs-2.31/ld/Options.html
The meaning of -O1 was explained in more detail in this LWN article:
https://lwn.net/Articles/192624/
Apparently it makes the resulting symbol table use a bigger hash
table, so the load factor is smaller and lookups are faster. Cool.
As for -Bsymbolic-functions, the documentation indicates that it's a
way of saving lookups through the symbol table entirely. There can
apparently be situations where it changes the behavior of a program,
specifically if the program relies on linker tricks to provide
customization features:
https://bugs.launchpad.net/ubuntu/+source/xfe/+bug/644645
https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=637184#35
But I'm pretty sure CPython doesn't permit that kind of trick: you
don't load a shared object that tries to redefine some symbol found
in the interpreter core.
The stronger reason I'm confident using -Bsymbolic-functions is
safe, though, is empirical. Both Debian and Ubuntu have been
shipping a Python built this way since forever -- it was introduced
for the Python 2.4 and 2.5 in Ubuntu "hardy", and Debian "lenny",
released in 2008 and 2009. In those 12 years they haven't seen a
need to drop this flag; and I've been unable to locate any reports
of trouble related to it, either on the Web in general or on the
Debian bug tracker. (There are reports of a handful of other
programs breaking with it, but not Python/CPython.) So that seems
like about as thorough testing as one could hope for.
---
As for the performance impact: I ran CPython upstream's preferred
benchmark suite, "pyperformance", in the same way as described in
the previous commit. On top of that commit's change, the results
across the 60 benchmarks in the suite are:
The median is 6% faster.
The middle half (aka interquartile range) is from 4% to 8% faster.
Out of 60 benchmarks, 3 come out slower, by 1-4%. At the other end,
5 are at least 10% faster, and one is 17% faster.
So, that's quite a material speedup! I don't know how big the
effect of these flags is for other software; but certainly CPython
tends to do plenty of dynamic linking, as that's how it loads
extension modules, which are ubiquitous in the stdlib as well as
popular third-party libraries. So perhaps that helps explain why
optimizing the dynamic linker has such an impact.
|
||
|---|---|---|
| .. | ||
| acl2 | ||
| angelscript | ||
| bats | ||
| ceptre | ||
| chibi | ||
| clips | ||
| clisp | ||
| clojure | ||
| clojurescript/lumo | ||
| dart | ||
| dhall | ||
| duktape | ||
| eff | ||
| elixir | ||
| erlang | ||
| evcxr | ||
| falcon | ||
| gauche | ||
| gnu-apl | ||
| groovy | ||
| gtk-server | ||
| guile | ||
| hugs | ||
| hy | ||
| icon-lang | ||
| io | ||
| j | ||
| janet | ||
| jimtcl | ||
| joker | ||
| jruby | ||
| jython | ||
| kona | ||
| lfe | ||
| lolcode | ||
| love | ||
| lua-5 | ||
| luajit | ||
| lush | ||
| maude | ||
| metamath | ||
| micropython | ||
| mujs | ||
| nix-exec | ||
| octave | ||
| perl | ||
| php | ||
| picoc | ||
| picolisp | ||
| pixie | ||
| proglodyte-wasm | ||
| pure | ||
| pyrex | ||
| python | ||
| qnial | ||
| quickjs | ||
| racket | ||
| rakudo | ||
| rascal | ||
| rebol | ||
| red | ||
| regina | ||
| renpy | ||
| ruby | ||
| scheme48 | ||
| scsh | ||
| self | ||
| spidermonkey | ||
| supercollider | ||
| tcl | ||
| tinyscheme | ||
| unicon-lang | ||
| wasmer | ||
| wasmtime | ||