mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: "Roy Sigurd Karlsbakk" <roy@karlsbakk.net>
To: ffmpeg-devel@lists.sourceforge.net
Cc: linux-kernel@vger.kernel.org
Subject: Re: [Ffmpeg-devel] [RFC] benchmark on athlon + intel xeon + Apple G4 + intel p3
Date: Sun, 24 Nov 2002 13:25:47 +0000	[thread overview]
Message-ID: <20021124.ZaY.84260300@mail.pronto.tv> (raw)

>Intel Pentium III Cu-mine 850MHz (on busy system)
>1.  bench: utime=87.380s
>2.  bench: utime=87.390s
>3.  bench: utime=87.440s
>avg bench: utime=87.403s

humtitim...
trying out on developer.skolelinux.no - a dual P III 997.5MHz (according to /proc/cpuinfo)
machine:

1. bench: utime=75.790s
2. bench: utime=76.570s
3. bench: utime=76.330s
avg. bench: utime=76.230s

>> K7: Hz*s/1000: 76.963
>> G4: Hz*s/1000: 80.223
>> P4: Hz*s/1000: 93.932
>  P3: Hz*s/1000: 74.293
P3(2): Hz*s/1000: 76.094

strange... this shows marginally lower performance on mine than yours, but it still beats the
lot, including the Athlon. Can anyone explain this???????????

I beleive there was some talk on lkml about some sort of P4 optimisation (interrupt stuff) that
wasn't enabled on 2.4, but comes along in 2.5. Any ideas??? (I cc:ed the lkml on this one)

>Hmm, P3 seems pretty fast in comparison and this was not tested on high-end
>system but standard Linux 2.4.18, P3 850, i440BX, 256MB SDRAM, 10GB 4200UPM
>HDD with lots of other apps running at the same time.

The system I was testing on had a load of around 1.2 or something, but given it's a system
with quite nice I/O and two 1GHz CPUs, I don't think it was important.

roy
--
Roy Sigurd Karlsbakk, Datavaktmester

Computers are like air conditioners.
They stop working when you open Windows.



                 reply	other threads:[~2002-11-24 13:17 UTC|newest]

Thread overview: [no followups] expand[flat|nested]  mbox.gz  Atom feed

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=20021124.ZaY.84260300@mail.pronto.tv \
    --to=roy@karlsbakk.net \
    --cc=ffmpeg-devel@lists.sourceforge.net \
    --cc=linux-kernel@vger.kernel.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

all inboxes | Powered by JetHome®