From: Gerhard Wiesinger <lists@wiesinger.com>
To: Paolo Bonzini <pbonzini@redhat.com>, qemu-devel@nongnu.org
Subject: Re: [Qemu-devel] QEMU/KVM performance gets worser - high load - high interrupts - high context switches
Date: Mon, 11 Jan 2016 22:04:26 +0100 [thread overview]
Message-ID: <569418DA.9070907@wiesinger.com> (raw)
In-Reply-To: <56936630.2030907@redhat.com>
On 11.01.2016 09:22, Paolo Bonzini wrote:
>
> On 09/01/2016 17:46, Gerhard Wiesinger wrote:
>> # Positive consequences via munin monitoring:
>> # Reduced fork rate: 40 => 13
>> # process states: running 15 => <1
>> # CÜU temperature: (core dependant) 65-70°C => 56-64°C
>> # CPU usage: system: 47% => 15%, user: 76% => 50%
>> # Context Switches: 20k => 7.5k
>> # Interrupts: 16k => 9k
>> # Load average: 2.8 => 1
>>
>> => back at the level before one year!!!!!!!
>>
>> Any idea why the serial device/PCI controller and the USB mouse tablet
>> consume so much CPU on latest kernel and/or qemu?
> For USB, it's possible that you're not using the USB autosuspend
> feature? (As explained in Gerd's blog post, for Microsoft OSes you may
> need to fiddle with the registry).
>
> For virtio-serial, I have no idea.
Linux VMs: All VMs are Linux VM on this KVM host, so as per blog post
udev rules should apply well for USB autosuspend. Most of the effect
came from the virtio-serial and not from USB tablet.
For another KVM host with a Windows 7 VM:
I tried to find apply the blog post: But there is no option "Allow the
computer to turn off the device to save power"
Nevertheless CPU usage could be reduced by removing the USB tablet from
the Win7 VM.
Ciao,
Gerhard
prev parent reply other threads:[~2016-01-11 21:05 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-12-08 9:39 [Qemu-devel] QEMU/KVM performance gets worser - high load - high interrupts - high context switches Gerhard Wiesinger
2015-12-11 8:03 ` Gerhard Wiesinger
2016-01-09 16:46 ` Gerhard Wiesinger
2016-01-11 8:22 ` Paolo Bonzini
2016-01-11 21:04 ` Gerhard Wiesinger [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=569418DA.9070907@wiesinger.com \
--to=lists@wiesinger.com \
--cc=pbonzini@redhat.com \
--cc=qemu-devel@nongnu.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;
as well as URLs for NNTP newsgroup(s).