public inbox for gentoo-dev@lists.gentoo.org
 help / color / mirror / Atom feed
From: Spider <spider@gentoo.org>
To: gentoo-dev@gentoo.org
Subject: Re: [gentoo-dev] GCC 3 Vs GCC 2 and some other stuff
Date: Mon, 8 Apr 2002 04:46:12 +0200	[thread overview]
Message-ID: <20020408044612.4489e915.spider@gentoo.org> (raw)
In-Reply-To: <F125KsD4cKbJWYumCRM0000ad86@hotmail.com>

[-- Attachment #1: Type: text/plain, Size: 2348 bytes --]

I know well that this is was completely unscientific and unreproductible
behaviour, with only one run and so on.

PDC20265: chipset revision 2
PDC20265: not 100% native mode: will probe irqs later
PDC20265: (U)DMA Burst Bit ENABLED Primary PCI Mode Secondary PCI Mode.
    ide2: BM-DMA at 0x7400-0x7407, BIOS settings: hde:DMA, hdf:pio
    ide3: BM-DMA at 0x7408-0x740f, BIOS settings: hdg:pio, hdh:pio

hde: Maxtor 5T030H3, ATA DISK drive
its an Athlon t-bird 1GHz
MemTotal:       288548 kB
(PC-100 SDRAM)

Filesystem on the drive used for compilations are ReiserFS.

Using r5 hash to sort names
ReiserFS version 3.6.25

also, the fact that I dont use the same compiler flags for both
compilers are a dead giveaway.

Better code, I can't speak for. More tests, I can, I've had to patch up
some c++ code in order to fit the stricter tests, something I consider
good.


cpu idle time doesn't matter much when diskaccess is ventured, should I
ever intend to do a good benchmark I'd use tmpfs for the whole process,
and make sure I dont run out of RAM while doing it. This is a user
comparsion, the feeling of how long things take to compile c++. 

And yes, the machine was in "normal use" at the time. Xchat, sylpheed
and some aterm's.  bad behaviour for a benchmarker. But standard for me
whenever I compile things, and thats how I wanted the comparsion done.

kernel is for once the default gentoo one, something I seldom use
normally. (I prefer -jam series)

//Spider



> 
> So, regarding your benchmarks Spider. There is something wrong,
> definately. And I think our gentoo kernel heads around here should
> take a close look at it. Sure, GCC 3.X *is* slower on compilation
> time, however, your tests show a very disturbing fact: Under some
> circumstances, your CPU seems to spend unreasonable amount of time not
> doing anything. This could be an indication of a bigger issue,
> possibly a configuration or a hardware issue. There might be an  issue
> going on with the cache or the filesystem or even the loader. How much
> memory the PC you used has and what kind of drive and filesystem did
> you use? (I hope that all this is not a side effect of one of the
> Gentoo kernel patches...)
> 


--
begin  happy99.exe
This is a .signature virus! Please copy me into your .signature!
See Microsoft KB Article Q265230 for more information.
end

[-- Attachment #2: Type: application/pgp-signature, Size: 189 bytes --]

  reply	other threads:[~2002-04-08  2:44 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2002-04-08  1:39 [gentoo-dev] GCC 3 Vs GCC 2 and some other stuff Eugenia Loli-Queru
2002-04-08  2:46 ` Spider [this message]
2002-04-08  5:00   ` Stacey Keast
2002-04-08  6:18     ` Spider
2002-04-08  5:33   ` Geert Bevin
2002-04-08 19:49     ` Spider
2002-04-08  9:54   ` Bart Verwilst
2002-04-08  9:57     ` Einar Karttunen
2002-04-08 16:46     ` Thilo Bangert

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=20020408044612.4489e915.spider@gentoo.org \
    --to=spider@gentoo.org \
    --cc=gentoo-dev@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