linuxppc-dev.lists.ozlabs.org archive mirror
 help / color / mirror / Atom feed
From: Kenneth Johansson <kenneth.johansson@inn.ericsson.se>
To: Dan Malek <dan@embeddededge.com>
Cc: Armin Kuster <akuster@mvista.com>,
	"linuxppc-embedded@lists.linuxppc.org"
	<linuxppc-embedded@lists.linuxppc.org>
Subject: Re: linuxppc_2_4_devel on walnut
Date: Fri, 16 Nov 2001 21:47:11 +0100	[thread overview]
Message-ID: <3BF57B4F.7B0ABCC@inn.ericsson.se> (raw)
In-Reply-To: 3BF4A2D4.5080302@embeddededge.com


Dan Malek wrote:
>
> Kenneth Johansson wrote:
>
> > But "time dd if=/dev/zero of=testing bs=1024k count=100" on a nfs mouted fs
> > used to be 18s and is now 21s, a 16% slowdown not that I care much but still
> > quite a large difference.
>
> What versions of kernels/drivers are you comparing?  Do you do this
> back-to-back with the same NFS server, or have you introduced more
> variables into your testing?  This is why specially prepared network
> performance testers are better suited for discussion.

This was to the same nfs server on a live network. I did the test only two
times on the first kernel version that was checke out a few hours before the
mail was posted last friday.

This was not done to benchmark anything but a way for me to verify what speed
the networks was using 10/100 Mb was at the time reported wrong by the
driver.

The reason I run it twice was that I thougt 5,5MB/s was not so great but the
second run had the same number. Then I upgraded the tree to a version that
had Armin Kusters changes and just for fun run the test again.

If I test only tcp/ip over the network I now get this..
----
walnut:/tmp# time dd if=/dev/zero  bs=1024k count=100 | nc -q0 <server> 9
100+0 records in
100+0 records out

real    0m14.838s
user    0m0.370s
sys     0m14.380s
---
6,7Mb/s

If I do the same from a intel 400MHz kernel 2.2.20 I get
---
[innkeon@spawn innkeon]$time dd if=/dev/zero  bs=1024k count=100 | nc -q0
<server> 9
100+0 records in
100+0 records out

real    0m12.838s
user    0m0.110s
sys     0m1.890s
---
7,8 MB/s

hmm funny the difference is also 16%

(nc is the netcat program.)

--
Kenneth Johansson
Ericsson Business Innovation AB   Tel: +46 8 404 71 83
Viderögatan 3                     Fax: +46 8 404 72 72
164 80 Stockholm                  kenneth.johansson@inn.ericsson.se

** Sent via the linuxppc-embedded mail list. See http://lists.linuxppc.org/

  reply	other threads:[~2001-11-16 20:47 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2001-10-29 16:35 linuxppc_2_4_devel on walnut Kenneth Johansson
2001-10-29 16:57 ` Tom Rini
2001-10-29 17:51 ` Armin Kuster
2001-11-07 17:39 ` Kenneth Johansson
2001-11-09 15:23   ` Kenneth Johansson
2001-11-14 17:01     ` Armin Kuster
2001-11-15 18:06       ` Kenneth Johansson
2001-11-16  5:23         ` Dan Malek
2001-11-16 20:47           ` Kenneth Johansson [this message]
  -- strict thread matches above, loose matches on Subject: below --
2001-11-07 17:47 Wright, David
2001-11-07 20:27 Martin, Tim

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=3BF57B4F.7B0ABCC@inn.ericsson.se \
    --to=kenneth.johansson@inn.ericsson.se \
    --cc=akuster@mvista.com \
    --cc=dan@embeddededge.com \
    --cc=linuxppc-embedded@lists.linuxppc.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;
as well as URLs for NNTP newsgroup(s).