On 2017-12-06 16:15, Robert T. McGibbon wrote:
There's a bit of tension between binary performance and compatibility. When facing this tradeoff, manylinux-1 obviously favors compatibility.
Agreed, but the weird thing here is that the manylinux precompiled Pillow .so libs are much faster than if Pillow was fully compiled on the machine locally, without any "optimizations" other than -march=native.
Only when -O3 is added to the local compilation does the performance match the one of .so libs coming from PyPi.
That's the weird part, and I was trying to figure out what exactly is being done to the officially precompiled libs, whether -O3 or something else was used, and why that which was used is not part of the official setup.py, but that's indeed the question for Pillow devs.
I asked here on this list first, because not seeing any compiler flags in the official sources (other than -O0 for debug makefile target), I thought maybe some optimizations are done by the (PyPi) packaging.
I've opened an issue in case anyone is interested in a follow up (or please let me know if you want me to update this thread with more info):
https://github.com/python-pillow/Pillow/issues/2879 Thanks. -- Vlad K. _______________________________________________ Wheel-builders mailing list Wheel-builders@python.org https://mail.python.org/mailman/listinfo/wheel-builders
