From: Neil Horman <nhorman@redhat.com>
To: Duv Dek <onur@ee.bilkent.edu.tr>
Cc: nfs@lists.sourceforge.net
Subject: Re: NFS response time
Date: Tue, 25 Jan 2005 16:43:50 -0500 [thread overview]
Message-ID: <41F6BD96.4040409@redhat.com> (raw)
In-Reply-To: <003a01c50326$73182550$7889b38b@alpin>
Duv Dek wrote:
> Hi
>
> We have a problem with our NFS server on Redhat 9. In case a program on
> the server uses high CPU, the NFS clients almost lock and nfs stops
> giving response until that program lowers its CPU usage. We tried to
> increase the priority of nfsd deamons with renice, and also tried to
> increase the number of nfsd threads, decreased the priority of the
> program using high CPU with renice, but none of them worked. How can
> we solve this problem so that nfs does not lock?
>
Have your tried to ascertain which process on your system is responsible
(or most responsible) for the high CPU utilization?
Neil
--
/***************************************************
*Neil Horman
*Software Engineer
*Red Hat, Inc.
*nhorman@redhat.com
*gpg keyid: 1024D / 0x92A74FA1
*http://pgp.mit.edu
***************************************************/
-------------------------------------------------------
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-01-25 21:43 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-01-25 21:40 NFS response time Duv Dek
2005-01-25 21:43 ` Neil Horman [this message]
2005-01-25 22:00 ` Duv Dek
2005-01-26 12:46 ` Neil Horman
-- strict thread matches above, loose matches on Subject: below --
2005-01-25 17:19 Duv Dek
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=41F6BD96.4040409@redhat.com \
--to=nhorman@redhat.com \
--cc=nfs@lists.sourceforge.net \
--cc=onur@ee.bilkent.edu.tr \
/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