From: "Klavs Klavsen" <kl@vsen.dk>
To: gentoo-dev@lists.gentoo.org
Subject: [gentoo-dev] Do we want optimal performance?
Date: Wed, 8 Sep 2004 12:15:59 +0200 (CEST) [thread overview]
Message-ID: <33333.10.0.0.51.1094638559.squirrel@10.0.0.51> (raw)
Hi guys,
Just read an interesting article about Xeon vs. Opteron from anandtech -
where they really show how much difference compile optimizations (or not)
does - and how it differs for different programs for different processors.
http://www.anandtech.com/linux/showdoc.aspx?i=2163&p=1
To me this clearly shows, that if Gentoo wants the best performance - we
can't use a "one cflags fits them all" approach. I do know that if a
program breaks, those CFLAGS are pulled out in the individual ebuild, but
this is not due to poor performance.
IMHO the only way for Gentoo to prove its true potential - is to somehow
build an array of compile options, with CPU's on X, programs on Y and
GCC-version on Z. Getting the numbers for each CPU, will ofcourse require
writing tests, for each program - but IMHO this can be done, if we do it
one at a time.
I would suggest these tests be included like the gentoo-stats program, as
something the individual Gentooist can choose to run after each compile -
which would give him the optimal performance (and recompile X number of
times to test different flags out) on his CPU/program/GCCversion
combination, and at the same time, send the result to a Gentoo database.
I know I would definetely have the patience to let it test and test again,
if it meant more performance for me Smile
The end result should be, that Gentoo automagically selects the optimal
CFLAGS (in performance and stability - perhaps with some optimizations
flagged as "unstable" so people can select "optimize for performance" vs.
"optimize for stability") depending on the X, Y and Z from above.
I would very much like to be one of the guys that gets the ball rolling,
but as I'm not a Gentoo Dev - We (or just I) need to agree with the Gentoo
Dev's on how this could best be done.
What do you think? am I crazy? It seems to me that the anandtech tests
shows that it is more than just a 1% or 2% difference, with the right
CFLAGS - and that the right CFLAGS for one program, can be the worst for
another on same CPU/GCC combination.
--
Regards,
Klavs Klavsen, GSEC - kl@vsen.dk - http://www.vsen.dk
PGP: 7E063C62/2873 188C 968E 600D D8F8 B8DA 3D3A 0B79 7E06 3C62
"Those who do not understand Unix are condemned to reinvent it, poorly."
--Henry Spencer
--
gentoo-dev@gentoo.org mailing list
next reply other threads:[~2004-09-08 10:16 UTC|newest]
Thread overview: 25+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-09-08 10:15 Klavs Klavsen [this message]
2004-09-08 11:29 ` [gentoo-dev] Do we want optimal performance? Paul de Vrieze
2004-09-08 12:03 ` Corvus Corax
2004-09-08 13:16 ` Paul de Vrieze
2004-09-08 12:19 ` Alin Nastac
2004-09-08 13:24 ` Marcus D. Hanwell
2004-09-08 13:43 ` Patrick Lauer
2004-09-08 14:21 ` Klavs Klavsen
2004-09-09 7:52 ` Paul de Vrieze
2004-09-08 12:49 ` Spider
2004-09-08 17:16 ` Robert Moss
2004-09-08 18:20 ` Chris Gianelloni
2004-09-08 19:11 ` Klavs Klavsen
2004-09-08 19:54 ` Paul de Vrieze
2004-09-08 20:05 ` Marcus D. Hanwell
2004-09-08 19:41 ` Lisa Seelye
2004-09-09 0:49 ` Daniel Goller
2004-09-09 1:51 ` [gentoo-dev] per package cflags (was Re: Do we want optimal performance?) Travis Tilley
2004-09-09 2:26 ` Robin H. Johnson
2004-09-09 3:42 ` Ned Ludd
2004-09-09 3:49 ` Robin H. Johnson
2004-09-09 17:23 ` Robert Moss
2004-09-09 4:41 ` Will Buckner
2004-09-09 4:51 ` Ciaran McCreesh
2004-09-09 6:07 ` [gentoo-dev] Do we want optimal performance? Klavs Klavsen
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=33333.10.0.0.51.1094638559.squirrel@10.0.0.51 \
--to=kl@vsen.dk \
--cc=gentoo-dev@lists.gentoo.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox