From: Avi Kivity <avi@redhat.com>
To: jmandawg <jmandawg@hotmail.com>
Cc: kvm@vger.kernel.org
Subject: Re: XP guests sluggish after around 1 week of uptime
Date: Mon, 19 Jan 2009 12:09:39 +0200 [thread overview]
Message-ID: <49745163.2090502@redhat.com> (raw)
In-Reply-To: <BAY102-DAV1327CAC2278BE42C0B5F76D2D30@phx.gbl>
jmandawg wrote:
> It's definitely some kind of Disk IO problem, I can't even copy a 700MB file
> on that guest without waiting a loooong time. Running bonnie on my linux
> guest shows considerable slow down in disk performance.
>
> Results after a fresh Reboot of the Host:
>
> root@wserver:~# cat bonnieresults.txt
> Version 1.03b ------Sequential Output------ --Sequential Input-
> --Random-
> -Per Chr- --Block-- -Rewrite- -Per Chr- --Block--
> --Seeks--
> Machine Size K/sec %CP K/sec %CP K/sec %CP K/sec %CP K/sec %CP /sec
> %CP
> wserver 1G 10617 23 12241 1 10328 2 47915 93 301061 93 5095
> 98
> ------Sequential Create------ --------Random
> Create--------
> -Create-- --Read--- -Delete-- -Create-- --Read---
> -Delete--
> files /sec %CP /sec %CP /sec %CP /sec %CP /sec %CP /sec
> %CP
> 16 +++++ +++ +++++ +++ +++++ +++ +++++ +++ +++++ +++ +++++
> +++
> wserver,1G,10617,23,12241,1,10328,2,47915,93,301061,93,5094.8,98,16,+++++,++
> +, +++++,+++,+++++,+++,+++++,+++,+++++,+++,+++++,+++
>
> Results after noticing considerable slow down on other guest machine:
>
> root@wserver:~# cat bonnieresults_SLOW.txt
> Version 1.03b ------Sequential Output------ --Sequential Input-
> --Random-
> -Per Chr- --Block-- -Rewrite- -Per Chr- --Block--
> --Seeks--
> Machine Size K/sec %CP K/sec %CP K/sec %CP K/sec %CP K/sec %CP /sec
> %CP
> wserver 1G 2252 3 3771 0 6844 1 46057 70 355858 50 752.3
> 7
> ------Sequential Create------ --------Random
> Create--------
> -Create-- --Read--- -Delete-- -Create-- --Read---
> -Delete--
> files /sec %CP /sec %CP /sec %CP /sec %CP /sec %CP /sec
> %CP
> 16 +++++ +++ +++++ +++ +++++ +++ +++++ +++ +++++ +++ +++++
> +++
> wserver,1G,2252,3,3771,0,6844,1,46057,70,355858,50,752.3,7,16,+++++,+++,++++
> +, +++,+++++,+++,+++++,+++,+++++,+++,+++++,+++
>
> After a reboot of the host, they guest are fine again, but for how long...
>
> Any advice or suggestions?
>
What does 'top' show for the guests? I'm interested in qemu's VIRT and
RES columns.
Also, 'vmstat 1' on host and guest while slow copying is happening.
--
error compiling committee.c: too many arguments to function
prev parent reply other threads:[~2009-01-19 10:09 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-01-12 4:12 XP guests sluggish after around 1 week of uptime Jay Mann
2009-01-12 8:58 ` Florent
2009-01-12 12:34 ` Jay
2009-01-12 13:36 ` Avi Kivity
2009-01-12 15:24 ` Jay
2009-01-13 9:29 ` Avi Kivity
[not found] ` <001501c9757a$eda76400$c8f62c00$@com>
2009-01-13 12:31 ` jmandawg
[not found] ` <007301c97982$f704b500$e50e1f00$@com>
2009-01-18 15:39 ` jmandawg
2009-01-19 12:05 ` Avi Kivity
[not found] ` <BAY102-DAV67C4CDA23F6EC8D7DB94DD2D30@phx.gbl>
2009-01-19 12:46 ` Avi Kivity
[not found] ` <000b01c97a35$df21a7f0$9d64f7d0$@com>
2009-01-19 13:00 ` jmandawg
2009-01-19 13:07 ` Avi Kivity
[not found] ` <000601c979ea$d67f60b0$837e2210$@com>
2009-01-19 4:03 ` jmandawg
2009-01-19 10:09 ` Avi Kivity [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=49745163.2090502@redhat.com \
--to=avi@redhat.com \
--cc=jmandawg@hotmail.com \
--cc=kvm@vger.kernel.org \
/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