From: Olaf Kirch <okir@suse.de>
To: Brad Barnett <lists@L8R.net>
Cc: nfs@lists.sourceforge.net
Subject: Re: knfsd brought to its knees, by a simple rsync or cp operation
Date: Wed, 2 Mar 2005 10:03:13 +0100 [thread overview]
Message-ID: <20050302090312.GA5003@suse.de> (raw)
In-Reply-To: <20050301181007.382a1422@be.back.l8r.net>
On Tue, Mar 01, 2005 at 06:10:07PM -0500, Brad Barnett wrote:
> > Well, it sounds like something's eating the network bandwidth,
> > or otherwise interfering with nfsd responsiveness. Again, are
> > you using UDP or TCP? If UDP, look at nfsstat output to see if
> > you have a high retransmit count.
> >
>
> In my original post, I did mention that I can copy large files (isos) over
> the network at excellent speeds. That is, I get over 6M/sec transfer
> speed...
Stil you won't answer: UDP or TCP? :-)
And the question about retransmits referred to the situation where you
see the slow-downs.
> > If it's really a problem with scheduling, it should make a difference
> > if you run the rsync job with lower priority, and/or renice the
> > nfsd threads to run with higher priority.
>
> You can't really renice the kernel nfsd threads though :((
renice -20 -p <pid of nfsd> works for me.
Olaf
--
Olaf Kirch | --- o --- Nous sommes du soleil we love when we play
okir@suse.de | / | \ sol.dhoop.naytheet.ah kin.ir.samse.qurax
-------------------------------------------------------
SF email is sponsored by - The IT Product Guide
Read honest & candid reviews on hundreds of IT Products from real users.
Discover which products truly live up to the hype. Start reading now.
http://ads.osdn.com/?ad_id=6595&alloc_id=14396&op=click
_______________________________________________
NFS maillist - NFS@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/nfs
next prev parent reply other threads:[~2005-03-02 9:03 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-02-26 13:28 knfsd brought to its knees, by a simple rsync or cp operation Brad Barnett
2005-02-28 10:06 ` Olaf Kirch
2005-02-28 15:23 ` Brad Barnett
2005-02-28 15:44 ` Olaf Kirch
2005-02-28 16:20 ` Brad Barnett
2005-03-01 9:55 ` Olaf Kirch
2005-03-01 11:57 ` Brad Barnett
2005-03-01 14:21 ` Roger Heflin
2005-03-01 14:37 ` Olaf Kirch
2005-03-01 23:10 ` Brad Barnett
2005-03-02 9:03 ` Olaf Kirch [this message]
2005-03-02 16:41 ` Brad Barnett
2005-03-01 15:04 ` Bill Rugolsky Jr.
2005-03-01 16:08 ` Bill Rugolsky Jr.
2005-03-01 23:38 ` Brad Barnett
2005-03-01 23:40 ` Brad Barnett
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=20050302090312.GA5003@suse.de \
--to=okir@suse.de \
--cc=lists@L8R.net \
--cc=nfs@lists.sourceforge.net \
/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.