Intel Core i7 AVX GCC Compiler Tuning Results

[phoronix]

Phoronix: Intel Core i7 AVX GCC Compiler Tuning Results

For those owners of Intel's latest-generation Core i3/i5/i7 "Sandy Bridge" processors, here's a quick look at the impact of some GCC tuning options specific to these latest AVX-enabled Intel processors...

http://www.phoronix.com/vr.php?view=MTA3NjE

[darkbasic]

Holy shit, I didn't expect such a boost with a simple compiler flag.

[russofris]

Holy shit, I didn't expect such a boost with a simple compiler flag.

As many gentoo users have found, compiler flags generally have one of the following effects.

1: No effect at all
2: The compiled binary does not work
3: The compiled binary is slower
4: The compiled binary is faster

In addition, performance increases often require certain combinations of compiler flags, making the tweak more complex than adding "-march"

I once had a bash script for a number of CLI binaries (notably ffmpeg, faac, flac) which would iterate through cflag combinations and compilers (gcc versus icc) After each iteration, the script would run an automated benchmark on the resulting binary. Results were dumped to a file and sorted. The issue that I ran into was that the results would change depending on factors such as platform arch, available memory, and CPU affinity. Other issues involved (pre)linking and libraries, killing misbehaving binaries, memory reclamation, etc.

Overall, a system with local optimizations performed approximately 50% better on average than a generic "-o2" solution. The problem is that you will never be able to find and fix all of the minor issues caused by the optimizations across all binaries to a level required by a distro. My conclusion was that compiler optimizations are of great benefit to single-task servers (a transcoding server in my case), but are currently out of reach for a general desktop.

Then I bought a Mac....

[Tgui]

As many gentoo users have found, compiler flags generally have one of the following effects.

1: No effect at all
2: The compiled binary does not work
3: The compiled binary is slower
4: The compiled binary is faster

In addition, performance increases often require certain combinations of compiler flags, making the tweak more complex than adding "-march"

I once had a bash script for a number of CLI binaries (notably ffmpeg, faac, flac) which would iterate through cflag combinations and compilers (gcc versus icc) After each iteration, the script would run an automated benchmark on the resulting binary. Results were dumped to a file and sorted. The issue that I ran into was that the results would change depending on factors such as platform arch, available memory, and CPU affinity. Other issues involved (pre)linking and libraries, killing misbehaving binaries, memory reclamation, etc.

Overall, a system with local optimizations performed approximately 50% better on average than a generic "-o2" solution. The problem is that you will never be able to find and fix all of the minor issues caused by the optimizations across all binaries to a level required by a distro. My conclusion was that compiler optimizations are of great benefit to single-task servers (a transcoding server in my case), but are currently out of reach for a general desktop.

Then I bought a Mac....

Incredible. Possible expected outcome is one option out of the entire set of options?! YOU DON'T SAY!!!!



I too then bought a Mac and love the little things like, sleep that works.

[devius]

Then I bought a Mac....

... and??...

I too then bought a Mac and love the little things like, sleep that works.

Funny, I keep reading everywhere that macs are pieces of technological wonder, but my Mac Mini fails to boot properly 1 out of 3 boots. It just stays in the grey screen forever. Also, I can't let it turn off the screen through DPMS otherwise the screen is never going to wake up again unless I reboot. On the other hand all my cheap homebuilt PCs running Ubuntu suspend and hibernate perfectly fine all the time.

[Veerappan]

... and??...



Funny, I keep reading everywhere that macs are pieces of technological wonder, but my Mac Mini fails to boot properly 1 out of 3 boots. It just stays in the grey screen forever. Also, I can't let it turn off the screen through DPMS otherwise the screen is never going to wake up again unless I reboot. On the other hand all my cheap homebuilt PCs running Ubuntu suspend and hibernate perfectly fine all the time.

Opposite experience here... I've got a 13" Core 2 Duo Macbook Pro and it sleeps/wakes perfectly, as does my wife's Sandy Bridge MBP (13"), and her old iBook (G4), and her brother's and mother's systems (All of them either in or previously in the publishing industry).

My desktop (Athlon x2 5000+, then Phenom II x3, then an x6 and Radeon 4850, then a 4770, then 6850) hasn't woken from sleep properly in the last few years, not even once... even with an Ubuntu reinstall and then an eventual replacement with Mint.

I won't say that sleep is universally broken on my PCs in Linux (most of the other ones work), but it is for this one.

[WorBlux]

As many gentoo users have found, compiler flags generally have one of the following effects.

1: No effect at all
2: The compiled binary does not work
3: The compiled binary is slower
4: The compiled binary is faster

In addition, performance increases often require certain combinations of compiler flags, making the tweak more complex than adding "-march"

I once had a bash script for a number of CLI binaries (notably ffmpeg, faac, flac) which would iterate through cflag combinations and compilers (gcc versus icc) After each iteration, the script would run an automated benchmark on the resulting binary. Results were dumped to a file and sorted. The issue that I ran into was that the results would change depending on factors such as platform arch, available memory, and CPU affinity. Other issues involved (pre)linking and libraries, killing misbehaving binaries, memory reclamation, etc.

Overall, a system with local optimizations performed approximately 50% better on average than a generic "-o2" solution. The problem is that you will never be able to find and fix all of the minor issues caused by the optimizations across all binaries to a level required by a distro. My conclusion was that compiler optimizations are of great benefit to single-task servers (a transcoding server in my case), but are currently out of reach for a general desktop.

Then I bought a Mac....

Did you try profile guided optimization? My guess it that may be the easiest way to get the best binary without resorting to potentially dangerous flags.

[AnonymousCoward]

Did you try profile guided optimization? My guess it that may be the easiest way to get the best binary without resorting to potentially dangerous flags.

PGO is great. Gives me an easy 5-10% performance boost when optimising wined3d (can't profile the entire wine app because of a bug). PGO works great with Dolphin as well.

[rxonda]

The real advantage of AVX is the wide of the registers. Its 256 bit and SmallPT didnt use SIMD.
So, for a real good review, you have to put some programs that use SIMD power.

[christian_frank]

PGO is great. Gives me an easy 5-10% performance boost when optimising wined3d (can't profile the entire wine app because of a bug). PGO works great with Dolphin as well.

Hi,

how did you get this going with wined3d only ?
Do you have some kind of howto ?

I'm very interested in +5-10% pef increease in the wine d3d area.
Im nowadays compiling wine with march=native but that doesnt give that much of an fps increase.


Many thanks,
Christian