All of lore.kernel.org
 help / color / mirror / Atom feed
From: Bernd Schubert <bernd-schubert@web.de>
To: Trond Myklebust <trond.myklebust@fys.uio.no>
Cc: nfs@lists.sourceforge.net
Subject: Re: client: 2.6.7 client much slower than 2.4.26
Date: Fri, 2 Jul 2004 00:32:25 +0200	[thread overview]
Message-ID: <200407020032.28335.bernd-schubert@web.de> (raw)
In-Reply-To: <1088718192.4349.91.camel@lade.trondhjem.org>

On Thursday 01 July 2004 23:43, you wrote:
> P=E5 to , 01/07/2004 klokka 17:18, skreiv Bernd Schubert:
> > benchmarks:
> >
> > copy a file to the server (2.6.7): ~ 3MB/s
> > copy a file to the server (2.4.26): ~ 9MB/s
> >
> > copy a file from the server (2.6.7): ~ 3MB/s
> > copy a file from the server (2.4.26): ~ 11MB/s
>
> Looks like the wire speeds on read/write are the same. How does the
> above compare to ttcp transfer speeds of a 300MB file?

Thanks, I didn't know about this tool and I think you are right, it seems t=
hat=20
the general network speed is much slower with 2.6.7:

2.4.26:
bernd@euklid bernd>nttcp -T taylor
     Bytes  Real s   CPU s Real-MBit/s  CPU-MBit/s   Calls  Real-C/s   CPU-=
C/s
l  8388608    0.70    0.06     95.2480   1118.4811    2048   2906.74   3413=
3.3
1  8388608    0.71    0.03     94.1283   2485.7897    5793   8125.38  21457=
9.4

2.6.7:
bernd@euklid bernd>nttcp -T taylor
     Bytes  Real s   CPU s Real-MBit/s  CPU-MBit/s   Calls  Real-C/s   CPU-=
C/s
l  8388608    2.67    2.64     25.1472     25.4046    2048    767.43     77=
5.3
1  8388608    2.67    0.03     25.1442   2237.3350    6145   2302.40  20486=
7.5

Its already too late, so I will do the 300MB test tomorrow, but I think the=
=20
numbers from the default 8MB test are already convincing.


> How much memory does this thing have? The main difference between 2.4.x

Somehow this system didn't like to have more than 2x128MB, when we added=20
another DIMM, the system crashed pretty often, though memtest86 showed no=20
problems.=20

> and 2.6.x is the fact that the 2.6.x caches a lot more data and for
> longer (the VM is what decides when to flush the cache).
> You might want to try twiddling around with the vm sysctl parameters to
> see if that makes a difference.
>

I will try to play with this over the weekend.


Thanks again a lot for your help!


Cheers,
	Bernd


-------------------------------------------------------
This SF.Net email sponsored by Black Hat Briefings & Training.
Attend Black Hat Briefings & Training, Las Vegas July 24-29 - 
digital self defense, top technical experts, no vendor pitches, 
unmatched networking opportunities. Visit www.blackhat.com
_______________________________________________
NFS maillist  -  NFS@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/nfs

      reply	other threads:[~2004-07-01 22:32 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2004-07-01 21:18 client: 2.6.7 client much slower than 2.4.26 Bernd Schubert
2004-07-01 21:43 ` Trond Myklebust
2004-07-01 22:32   ` Bernd Schubert [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=200407020032.28335.bernd-schubert@web.de \
    --to=bernd-schubert@web.de \
    --cc=nfs@lists.sourceforge.net \
    --cc=trond.myklebust@fys.uio.no \
    /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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.