In a performance-critical situation like this, compiling Pillow from source specifically for your production box using a up-to-date compiler toolchain that can target your specific processor generation (-march=native or similar) is probably a win. There's a bit of tension between binary performance and compatibility. When facing this tradeoff, manylinux-1 obviously favors compatibility.
On Wed, Dec 6, 2017 at 6:33 AM, Vlad K. <[email protected]> wrote: > On 2017-12-06 12:03, Nathaniel Smith wrote: > >> >> I think your best bet is to ask the Pillow developers, or whoever >> builds their wheels for distribution. >> > > Thanks, I'll do that. > > > -- > Vlad K. > > _______________________________________________ > Wheel-builders mailing list > [email protected] > https://mail.python.org/mailman/listinfo/wheel-builders > -- -Robert
_______________________________________________ Wheel-builders mailing list [email protected] https://mail.python.org/mailman/listinfo/wheel-builders
