From: Avi Kivity <avi@redhat.com>
To: David Cure <kvm@cure.nom.fr>
Cc: kvm@vger.kernel.org
Subject: Re: performance trouble
Date: Mon, 30 Jan 2012 19:21:20 +0200 [thread overview]
Message-ID: <4F26D190.4040207@redhat.com> (raw)
In-Reply-To: <20120130165140.GJ26955@nfs-rbx.ovh.net>
On 01/30/2012 06:51 PM, David Cure wrote:
> Le Mon, Jan 30, 2012 at 10:20:34AM -0600, Brian Jackson ecrivait :
> >
> > Without more info or some way to reproduce the problem, it would be pointless
> > for one of the devs to spend much time on it.
>
> yes for sure.
>
> But I mean there is some way to trace at the KVM level what happens when the
> program runs in the VM ? And perhaps with these infos some one see the
> problem ;) (because with the upgrade of KVM/qemu we already cut the
> response time by 2).
>
Start with top and vmstat to see if the cpu or I/O are the bottleneck
(also helpful to run the Windows performance monitor in the guest). If
it's the cpu, run kvm_stat and report its output.
--
error compiling committee.c: too many arguments to function
next prev parent reply other threads:[~2012-01-30 17:21 UTC|newest]
Thread overview: 74+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-01-23 8:28 performance trouble David Cure
2012-01-23 10:04 ` David Cure
2012-01-30 15:36 ` David Cure
2012-01-30 16:20 ` Brian Jackson
2012-01-30 16:51 ` David Cure
2012-01-30 17:21 ` Avi Kivity [this message]
2012-01-31 17:15 ` David Cure
2012-01-31 17:21 ` Avi Kivity
2012-02-02 10:41 ` David Cure
2012-02-03 8:59 ` David Cure
2012-02-05 9:38 ` Avi Kivity
2012-02-10 10:09 ` David Cure
2012-02-14 13:32 ` Avi Kivity
2012-02-14 13:40 ` Gleb Natapov
2012-02-16 8:55 ` David Cure
2012-02-16 9:01 ` Gleb Natapov
2012-02-17 8:59 ` David Cure
2012-02-17 10:07 ` Gleb Natapov
2012-02-17 14:01 ` David Cure
2012-02-19 9:13 ` Gleb Natapov
2012-02-22 16:33 ` David Cure
2012-02-22 16:58 ` David Cure
2012-02-23 8:38 ` Gleb Natapov
2012-03-16 10:13 ` David Cure
2012-03-19 10:51 ` Gleb Natapov
2012-03-20 9:32 ` David Cure
2012-03-20 9:45 ` Gleb Natapov
2012-03-20 11:18 ` David Cure
2012-03-20 12:38 ` Gleb Natapov
2012-03-21 11:10 ` David Cure
2012-03-21 17:31 ` Peter Lieven
2012-03-22 7:53 ` Gleb Natapov
2012-03-22 7:57 ` Peter Lieven
2012-03-22 8:35 ` David Cure
2012-03-22 8:33 ` David Cure
2012-03-22 8:50 ` Peter Lieven
2012-03-22 8:48 ` Vadim Rozenfeld
2012-03-22 8:52 ` Peter Lieven
2012-03-22 9:38 ` Vadim Rozenfeld
2012-03-26 17:00 ` Peter Lieven
2012-03-26 17:46 ` Vadim Rozenfeld
2012-03-26 17:52 ` Gleb Natapov
2012-03-26 18:36 ` Vadim Rozenfeld
2012-03-26 18:54 ` Peter Lieven
2012-03-26 20:11 ` Vadim Rozenfeld
2012-03-27 8:56 ` Gleb Natapov
2012-03-27 9:23 ` Vadim Rozenfeld
2012-03-27 9:24 ` Gleb Natapov
2012-03-27 9:26 ` Peter Lieven
2012-03-27 10:00 ` Gleb Natapov
2012-03-27 12:20 ` Peter Lieven
2012-03-27 12:26 ` Gleb Natapov
2012-03-27 12:28 ` Peter Lieven
2012-03-27 12:29 ` Gleb Natapov
2012-03-27 12:30 ` Peter Lieven
2012-03-27 14:06 ` Peter Lieven
2012-03-27 15:44 ` Vadim Rozenfeld
2012-03-27 15:58 ` Peter Lieven
2012-03-27 16:12 ` Vadim Rozenfeld
2012-03-27 16:16 ` Peter Lieven
2012-03-27 17:06 ` Vadim Rozenfeld
2012-03-28 8:38 ` Peter Lieven
2012-03-27 10:40 ` Vadim Rozenfeld
2012-03-27 10:49 ` Peter Lieven
2012-03-27 11:43 ` Vadim Rozenfeld
2012-03-27 14:44 ` Peter Lieven
2012-03-27 15:37 ` Vadim Rozenfeld
2012-03-27 15:39 ` Peter Lieven
2012-03-27 15:55 ` Vadim Rozenfeld
2012-03-22 8:31 ` David Cure
2012-03-22 8:47 ` Peter Lieven
2012-02-14 13:48 ` Vadim Rozenfeld
2012-02-17 15:27 ` David Cure
2012-02-16 9:10 ` David Cure
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=4F26D190.4040207@redhat.com \
--to=avi@redhat.com \
--cc=kvm@cure.nom.fr \
--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 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.