From: Nick Piggin <piggin@cyberone.com.au>
To: Huo Zhigang <zghuo@ncic.ac.cn>
Cc: linux-kernel@vger.kernel.org
Subject: Re: lmbench 2.4.20-8(RH9), 2.4.20, 2.6.0
Date: Sat, 20 Dec 2003 14:55:44 +1100 [thread overview]
Message-ID: <3FE3C840.4000702@cyberone.com.au> (raw)
In-Reply-To: <20031220034548.GA4809@lucent>
Huo Zhigang(???) wrote:
>Howdy,
>
>Is the network performance of 2.6.0 so bad or my test
>totally wrong?
>
>Could anyone tell me how to dig into performance
>optimization of linux?
>
This has come up a few times, but nobody is too worried about it.
I have profiles showing that more than double the amount of time
is spent in copying data for the same amount of work.
Its worth noting though, that it is "networking" over localhost.
I expect the numbers for remote networking are better, but don't
have a good network setup to test it.
Do you have any real applications (not benchmarks) that have
performance problems?
prev parent reply other threads:[~2003-12-20 3:55 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-12-20 3:45 lmbench 2.4.20-8(RH9), 2.4.20, 2.6.0 Huo Zhigang(霍志刚)
2003-12-20 3:55 ` Nick Piggin [this message]
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=3FE3C840.4000702@cyberone.com.au \
--to=piggin@cyberone.com.au \
--cc=linux-kernel@vger.kernel.org \
--cc=zghuo@ncic.ac.cn \
/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