On Sunday, November 10, 2019, Kevin Kofler <kevin.kofler@xxxxxxxxx> wrote:
Frantisek Zatloukal wrote:
> How is statically linked libpython hack? It's just a different way to do
> it, isn't it?
It means you are shipping 2 copies of the Python interpreter, one statically
linked into the python3 binary and one as a shared library. This is much
less elegant than shipping a single shared copy of the code.
You also need to actually build all the code twice to actually get the
performance improvements, because if you just statically link the PIC
objects (built for the shared library) into the binary, the performance will
not noticeably improve.
> And if toolchain needs some improving, fine, but why should we have lower
> performance and keep waiting on it if there is a solution available right
> now?
Because sometimes it is better to wait a bit for an elegant solution than to
rush out a quick hack that we then end up stuck with.
> And size increase? It's so tiny, I can't imagine why should that matter at
> all.
We are talking about megabytes! That is not tiny at all!
It is - even ssd storage is reasonably cheap nowadays.
Other changes like "upgrade foo to n+1" are most likely also increase size no one seem to care because it's not that written in the change proposal.
Anyways the performance win here easily justifies the tine space increase that no one would notice in practice.
_______________________________________________ devel mailing list -- devel@xxxxxxxxxxxxxxxxxxxxxxx To unsubscribe send an email to devel-leave@xxxxxxxxxxxxxxxxxxxxxxx Fedora Code of Conduct: https://docs.fedoraproject.org/en-US/project/code-of-conduct/ List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines List Archives: https://lists.fedoraproject.org/archives/list/devel@xxxxxxxxxxxxxxxxxxxxxxx
