From: Kip Macy <kip.macy@gmail.com>
To: Tupshin Harper <tupshin@tupshin.com>
Cc: Rik van Riel <riel@redhat.com>, xen-devel@lists.sourceforge.net
Subject: Re: horrible nfs server performance on domU
Date: Sat, 5 Mar 2005 19:03:27 -0800 [thread overview]
Message-ID: <b1fa291705030519035ade63b6@mail.gmail.com> (raw)
In-Reply-To: <422A71D4.3060708@tupshin.com>
Write allocation can get pretty challenging when there is no space to allocate.
On Sat, 05 Mar 2005 18:58:28 -0800, Tupshin Harper <tupshin@tupshin.com> wrote:
> Rik van Riel wrote:
>
> >On Sat, 5 Mar 2005, Tupshin Harper wrote:
> >
> >
> >
> >>>Time to try out whether profiling works in domU, so we can
> >>>figure out exactly where cpu time is being spent. I'm willing
> >>>to help you debug this problem.
> >>>
> >>>
> >>>
> Doh...major false alarm. Sorry. Turns out it was a 100% full root volume
> in the domU. That said, I'm rather surprised that it turned into 100%
> cpu utilization. FWIW, it's and XFS volume.
>
> -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
> _______________________________________________
> Xen-devel mailing list
> Xen-devel@lists.sourceforge.net
> https://lists.sourceforge.net/lists/listinfo/xen-devel
>
-------------------------------------------------------
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
prev parent reply other threads:[~2005-03-06 3:03 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-03-05 1:49 horrible nfs server performance on domU Tupshin Harper
2005-03-05 21:55 ` 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 [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=b1fa291705030519035ade63b6@mail.gmail.com \
--to=kip.macy@gmail.com \
--cc=riel@redhat.com \
--cc=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.