From: Tupshin Harper <tupshin@tupshin.com>
To: xen-devel@lists.sourceforge.net
Subject: horrible nfs server performance on domU
Date: Fri, 04 Mar 2005 17:49:37 -0800 [thread overview]
Message-ID: <42291031.4050805@tupshin.com> (raw)
I have the following setup:
* amd64 machine with 1.5GB ram and 10 ide drives combined into a few
software raid five arrays
* 2 lvm volume groups managed by the dom0. One for the domU volumes and
another for the domU swap partitions
* 1 lvm volume group managed by a domU that acts as a fileserver (nfs,
samba) to other domUs as well as devices onthe local lan
the "fileserver" domU has 256Mb allocated with 512MB of swap. I'm gettin
horrendous nfs performance (samba not really tested yet), and the
fileserver domU frequently is pegged at 99+% system cpu all being use by
pdflush. The swap is active but is not being used.
I'm running xen-unstable as of a couple weeks ago, and using
linux-2.6.10-xen + ac patches to get some needed driver support (all
disks have dma enabled).
right now, i'm looking at top on the fileserver, and even though there
is virtually no nfs or other network activity, and hasn't been for 10
minutes, pdflush is still maxing the cpu.
Any suggestions?
-Tupshin
-------------------------------------------------------
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
next reply other threads:[~2005-03-05 1:49 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-03-05 1:49 Tupshin Harper [this message]
2005-03-05 21:55 ` horrible nfs server performance on domU Rik van Riel
2005-03-05 22:17 ` Tupshin Harper
2005-03-06 0:14 ` Rik van Riel
2005-03-06 2:58 ` Tupshin Harper
2005-03-06 3:03 ` Kip Macy
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=42291031.4050805@tupshin.com \
--to=tupshin@tupshin.com \
--cc=xen-devel@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.