What flags are each and what version of GCC? Can you give the specific times and uname -a?
Announcement
Collapse
No announcement yet.
Benchmarks Of The Gentoo-based Sabayon
Collapse
X
-
Originally posted by Apopas View PostWell I learnt everything I know about gcc and icc flags and optimizations in general. A source based distro helps a lot there.
Also, I have not find a benefit yet to use Arch instead of Sabayon which is a binary edition of Gentoo.
Besides, Arch has AUR which contains packages to build from source, so you get to learn about USE flags and similar stuff anyway.
As to Sabayon vs Arch... no idea. Maybe a user of both can give some insight to the benefits of either distro, but so far it seems they are about on par to me.
Comment
-
a meant average feeling
Just boot faster, open programs faster, anything is faster
may be not 25%, but ~10%.
Anyway, i just like it.
It gives me the best answer. I started with Debian (Red Hat and Suse failed to stay) and all those little things that were disturbing me, are not there.
I'm surprised to see that a lot of people using Slack, Arch Gentoo
Comment
-
Originally posted by Apopas View PostWhat flags are each and what version of GCC? Can you give the specific times and uname -a?
Gentoo flags -march=amdfam10 -O2 -pipe
Default suse flags -O2 -g -m64 -fmessage-length=0 -D_FORTIFY_SOURCE=2 -fstack-protector -funwind-tables -fasynchronous-unwind-tables
AMD encode time=933 seconds
Gentoo encode time=950 seconds
suse defaults=952 seconds
2.6.31.5-0.1 desktop #1 SMP PREEMPT
GCC 4.4.2
Comment
-
Originally posted by BlackStar View PostI don't think compilation flags are all that useful. Setting up user accounts, desktop environments, understanding the boot sequence, device detection, the unix philosophy (everything is a file, no output unless something fails, permissions) - that's useful. Gcc/Icc flags, not so much (unless you are a developer) .
Besides, Arch has AUR which contains packages to build from source, so you get to learn about USE flags and similar stuff anyway.
As to Sabayon vs Arch... no idea. Maybe a user of both can give some insight to the benefits of either distro, but so far it seems they are about on par to me.
Comment
-
Originally posted by deanjo View PostJust for example I just compiled a couple handbrake (and it's supporting libraries which is extremely easy to do since it builds them specifically for hb use) using the recommended gentoo flags for Phenom II's. I then ran the same encode using the prepackaged rpm vs gentoos recommended vs AMD's recommended aggressive flags. Net result was a delta of 2% between the best version (AMD agressive flags) and worst versions (rpm and Gentoo recommended which were within seconds of each other and fall within standard deviation).
Comment
-
Originally posted by BlackStar View PostI don't think compilation flags are all that useful. Setting up user accounts, desktop environments, understanding the boot sequence, device detection, the unix philosophy (everything is a file, no output unless something fails, permissions) - that's useful. Gcc/Icc flags, not so much (unless you are a developer) .
Besides, Arch has AUR which contains packages to build from source, so you get to learn about USE flags and similar stuff anyway.
As to Sabayon vs Arch... no idea. Maybe a user of both can give some insight to the benefits of either distro, but so far it seems they are about on par to me.
Comment
-
Originally posted by deanjo View PostAMD recommended -march=amdfam10 -mabm -msse4a
Gentoo flags -march=amdfam10 -O2 -pipe
Default suse flags -O2 -g -m64 -fmessage-length=0 -D_FORTIFY_SOURCE=2 -fstack-protector -funwind-tables -fasynchronous-unwind-tables
AMD encode time=933 seconds
Gentoo encode time=950 seconds
suse defaults=952 seconds
2.6.31.5-0.1 desktop #1 SMP PREEMPT
GCC 4.4.2
Comment
-
Originally posted by XorEaxEax View PostWell, handbrake is rather pointless to use for this since the libraries it uses contains a ton of hand-optimized assembly code for all the time critical parts. So unless you explicitly tells the packages not to use hand-optimized assembly it will be worthless as a comparison between compiler options.
Comment
-
From gcc flags you are not going ofcourse to get 25% boost. But the small advantage you get in combination with the lean system which means less CPU and memory usage you get a bonus which is obvious in some applications, especially games, Firefox etc, boot times, start up times and your desktop in general feels faster.
The best always is to find a formula to apply different system flags for different parts of the system. For example while I build my system with Gentoo's defaults, my encoders are compiled with O3.
I run a similar test with lame. Gcc 4.4.2 and Kernel 2.6.32.
SUSE defaults = 0m35.996s
Gentoo defaults = 0m35.080s
Gentoo with O3 = 0m34.928s
The difference finally is about 3% better performance. Not something exceptional, but why not since I can have it easily? In games the FPS are even higher, especially in opensource games that I compiled myself.
Also, my system boots in 22 seconds (grub to gdm) plus 8 secs for KDE. Not bad for a 5 years old CPU.
Also, with Gentoo is easy to use ICC. The results are even better, but I can't since I avoid proprietary apps.Last edited by Apopas; 04 January 2010, 09:12 PM.
Comment
Comment