From: Rik van Riel <riel@redhat.com>
To: xen-devel@lists.xensource.com
Subject: Re: VT is comically slow
Date: Mon, 03 Jul 2006 04:48:57 -0400 [thread overview]
Message-ID: <44A8D9F9.4020603@redhat.com> (raw)
In-Reply-To: <44A8D54A.3000100@redhat.com>
Rik van Riel wrote:
> VT by itself seems fine, but once a VT domain is running a workload that
> is network intensive combined with a disk/cpu intensive workload, things
> get incredibly slow.
>
> Operations that take less than a second with either workload running
> alone can now take many seconds, sometimes the better part of a minute!
>
> Is this some limitation of the qemu device model?
Looking at it a bit more closely, it appears that postgresql
doing disk IO from inside a fully virtualized domain totally
kills the CPU.
It gets so bad that a simple "dmesg" takes 10-20 seconds to start,
and after that it spews data maybe 7 or 8 lines every other second.
Actually slower than serial console...
This is totally unusable :(
--
"Debugging is twice as hard as writing the code in the first place.
Therefore, if you write the code as cleverly as possible, you are,
by definition, not smart enough to debug it." - Brian W. Kernighan
next prev parent reply other threads:[~2006-07-03 8:48 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-07-03 8:28 VT is comically slow Rik van Riel
2006-07-03 8:48 ` Rik van Riel [this message]
2006-07-03 8:58 ` Keir Fraser
2006-07-03 10:31 ` Daniel Veillard
2006-07-03 14:14 ` Rik van Riel
2006-07-03 14:43 ` Petersson, Mats
2006-07-03 19:16 ` Rik van Riel
2006-07-04 7:03 ` Keir Fraser
2006-07-03 15:10 ` Keir Fraser
-- strict thread matches above, loose matches on Subject: below --
2006-07-06 19:16 alex
2006-07-06 20:59 ` Anthony Liguori
2006-07-10 7:51 ` Rami Rosen
2006-07-07 1:43 alex
2006-07-07 12:19 ` Anthony Liguori
2006-07-07 2:35 alex
2006-07-11 12:30 ` Horms
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=44A8D9F9.4020603@redhat.com \
--to=riel@redhat.com \
--cc=xen-devel@lists.xensource.com \
/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.