From: Nick Piggin <nickpiggin@yahoo.com.au>
To: Gergely Czuczy <phoemix@harmless.hu>
Cc: linux-kernel@vger.kernel.org
Subject: Re: Linux 2.4 VS 2.6 fork VS thread creation time test
Date: Sun, 23 May 2004 19:38:56 +1000 [thread overview]
Message-ID: <40B07130.6020408@yahoo.com.au> (raw)
In-Reply-To: <Pine.LNX.4.60.0405231058530.25386@localhost>
Gergely Czuczy wrote:
> On Sun, 23 May 2004, Nick Piggin wrote:
>
>
>>Gergely Czuczy wrote:
>>
>>>Box B is a lot better, but it doesn't metter according to the test,
>>>because the aim was to get the ratio of the two times with different
>>>sample rates.
>>>
>>
>>Even so, you really should be using the same system if you want
>>comparable results. The pentium 4 in particular can do worse at
>>specific things in microbenchmarks.
>
> It doesn't matter. That's why you should look at the "ratio" at the end
> and not on the pure numbers, they are just bonus "information"
>
I understand that... but the P4 might execute the fork test
relatively slower than the thread test compared to the P3.
Different CPU architectures, cache types and sizes, memory
to CPU speeds, etc. might all have some influcene on the
ratio.
next prev parent reply other threads:[~2004-05-23 9:39 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-05-23 7:57 Linux 2.4 VS 2.6 fork VS thread creation time test Gergely Czuczy
2004-05-23 8:55 ` Nick Piggin
2004-05-23 9:03 ` Gergely Czuczy
2004-05-23 9:38 ` Nick Piggin [this message]
2004-05-23 15:08 ` Anton Blanchard
2004-05-23 9:39 ` Christian Borntraeger
2004-05-23 10:00 ` David Lang
2004-05-23 19:47 ` Christian Borntraeger
2004-05-24 0:06 ` David Lang
[not found] ` <1085325156.622.0.camel@boxen>
[not found] ` <D53BF43BC70DD511A22500508BB3C0070A73CE83@wlvexc00.diginsite.com>
2004-05-24 7:15 ` David Lang
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=40B07130.6020408@yahoo.com.au \
--to=nickpiggin@yahoo.com.au \
--cc=linux-kernel@vger.kernel.org \
--cc=phoemix@harmless.hu \
/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