public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Matthias Welk <welk@fokus.gmd.de>
To: Trond Myklebust <trond.myklebust@fys.uio.no>
Cc: Matthias Welk <welk@fokus.gmd.de>, linux-kernel@vger.kernel.org
Subject: Re: nfs slowdown since 2.5.4
Date: Wed, 05 Jun 2002 13:50:14 +0200	[thread overview]
Message-ID: <3CFDFAF6.8090801@fokus.fhg.de> (raw)
In-Reply-To: <200206041253.44446.welk@fokus.gmd.de> <200206041848.38954.trond.myklebust@fys.uio.no> <200206041916.29725.welk@fokus.gmd.de> <200206041928.54392.trond.myklebust@fys.uio.no>

[-- Attachment #1: Type: text/plain, Size: 1343 bytes --]

Trond Myklebust wrote:

>On Tuesday 04 June 2002 19:16, Matthias Welk wrote:
>  
>
>>On Tuesday 04 June 2002 18:48, Trond Myklebust wrote:
>>    
>>
>>>On Tuesday 04 June 2002 17:56, Matthias Welk wrote:
>>>      
>>>
>>>>To get more info about this problem I compared the compile time and the
>>>>nfs traffic between 2.4.18-4 and 2.5.20 on a RedHat 7.3 system.
>>>>The sources (mosfet-liquid0.9.5.tar.gz - KDE style) were located on the
>>>>local disc and the libraries were linked over nfs.
>>>>The results attached to this mail show the big difference !
>>>>        
>>>>
>
>Does the appended patch make a difference
>

Yes, the lookup rate increased 1/3 compared to the unpatched version.
I have attached updated results of the build process, because there was a
mistake for the 2.4.18 version.

Now the addition to my last mail:

NFS-Server:        Auspex NS3010
NFS-Filesystem:    Auspex-specific (FastFLO Journaling File System)

Greetings, Matthias
---------------------------------------------------------------
From: Matthias Welk                   office:  +49-30-3463-7272
      FHG Fokus                       mobile:  +49-179- 1144752
      Kaiserin-Augusta-Allee 31       fax   :  +49-30-3463-8672
      10589 Berlin                    email : welk@fokus.fhg.de
----------------------------------------------------------------


[-- Attachment #2: build_2.4.18.txt --]
[-- Type: text/plain, Size: 198 bytes --]

#time to build on a RedHat 7.3 system with 2.4.18-4

real	1m8.473s
user	0m51.510s
sys	0m7.800s

# packets:	7757
lookup:		2952
getattr:	175
readdir:	72
readlink:	119
read:		567
frag:		4144
other:		0

[-- Attachment #3: build_2.5.20.txt --]
[-- Type: text/plain, Size: 213 bytes --]

#time to build on a RedHat 7.3 system with 2.5.20

real    1m48.509s
user    0m51.320s
sys     0m12.790s

# packets:	149859
lookup:		143791
getattr:	1273
readdir:	24
readlink:	119
read:		828
frag:		4232
other:		0

[-- Attachment #4: build_2.5.20_patched.txt --]
[-- Type: text/plain, Size: 220 bytes --]

#time to build on a RedHat 7.3 system with 2.5.20 patched

real    2m11.262s
user    0m50.960s
sys     0m14.260s

# packets:	234552
lookup:		229030
getattr:	728
readdir:	24
readlink:	119
read:		827
frag:		4231
other:		0

  reply	other threads:[~2002-06-05 11:50 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2002-06-04 10:53 nfs slowdown since 2.5.4 Matthias Welk
2002-06-04 12:23 ` Trond Myklebust
2002-06-04 15:56   ` Matthias Welk
2002-06-04 16:48     ` Trond Myklebust
2002-06-04 17:16       ` Matthias Welk
2002-06-04 17:28         ` Trond Myklebust
2002-06-05 11:50           ` Matthias Welk [this message]
2002-06-05 12:16             ` Trond Myklebust

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=3CFDFAF6.8090801@fokus.fhg.de \
    --to=welk@fokus.gmd.de \
    --cc=linux-kernel@vger.kernel.org \
    --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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox