11–18 of 18 posts
Am I totally misunderstanding something or there is no Dockerfile referenced? If so, is this just a binary blob I pull from a public registry? I have some trust concerns about basing my infrastructure on something opaque.
Absolutely! Was just an oversight on our part, here is the Dockerfile and build info https://github.com/revsys/optimized-python-docker
Another alternative for a fast speed up by changing your base image is trying out the pypy images.
This was just mentioned today at north bay python. Another alternative for a fast speed up by changing your base image is trying out the pypy images.
This was just mentioned today at north bay python. Another alternative for a fast speed up by changing your base image is trying out the pypy images.
Yeah I thought it would be nice to release this at North Bay today. We also released our new website redesign (and new infrastructure setup) last night so there is probably some dust on a few things we'll clean up over the next few days.
The 10%ish speed boost is all down to PGO, I'm assuming?
Profile-guided optimization, in layman terms, means that you run you code under a profiler for a while, see what parts (branches, functions, data structures etc) are being used the most and use this information to make a build of your code that considers the profiler's findings when doing optimization.
So what does it mean? It means, basically, that revsys is publishing a python build that is optimized for their use-case. Which may or may not be your use-case. This is not good nor bad.
Still, the claim "up to 19% faster" is false in general (but true in a particular case -- their use case).
Just keep this in mind, because this python build might perform worse than a regular python build.
So I see that profile-guided optimization are being used. Profile-guided optimization, in layman terms, means that you run you code under a profiler for a while, see what parts (branches, functions, data structures etc) are being used the most and use this information to make a build of your code that considers the profiler's findings when doing optimization. So what does it mean? It means, basically, that revsys is…
We did 10 runs of each on a large AWS instance and averaged the results.
The build info and benchmark results are up here https://github.com/revsys/optimized-python-docker if we’re wrong about something please let us know.
However, definitely agree that any optimization like this could have negative performance consequences for certain specific bits of code. But that’s likely true of any build to the next.