Hacker News Reader

Anyone who is using a distro package of pg has the largest opportunity because they are all built wrong. A peak-optimized binary will get you much more than 4% speed up over generic packages.

View on HN

Can you please elaborate, what’s wrong and what do I need to do when building from source?

compile with --march=native can often be significant.

Compiling for your target is good, not using the PLT for mem* functions helps a ton, feedback-directed optimization and LTO and/or post-link optimization helps the most. For CPU-bound workloads of course.

Will native march option work in case of cloud where you're not in control of cpu?

I haven't used a cloud where you don't dictate the exact CPU you want. EC2, GCE, and Azure all provide specific guarantees. Even if you wanted a generic any-cloud binary you would probably compile with -march=skylake or, if truly paranoid, sandybridge.

Many distro packages are, by contrast, compiled for k8-generic. Freaking Opteron!

BTW "native" is not really recommendable. One really ought to target a particular platform.

Do google and AWS hosted postgres do this? I assume, but I am not sure how to check.

I don't know but it would be out-of-character for Google to have a C program that wasn't optimized to the hilt.

Using PG for years and this is the first time somebody made me aware of this, so thank you.

Reply on news.ycombinator.com