This is an archived copy of the Xen.org mailing list, which we have preserved to ensure that existing links to archives are not broken. The live archive, which contains the latest emails, can be found at http://lists.xen.org/
Home Products Support Community News


Re: [Xen-devel] VT is comically slow

To: Rik van Riel <riel@xxxxxxxxxx>
Subject: Re: [Xen-devel] VT is comically slow
From: Keir Fraser <Keir.Fraser@xxxxxxxxxxxx>
Date: Mon, 3 Jul 2006 16:10:38 +0100
Cc: xen-devel@xxxxxxxxxxxxxxxxxxx
Delivery-date: Mon, 03 Jul 2006 08:10:56 -0700
Envelope-to: www-data@xxxxxxxxxxxxxxxxxx
In-reply-to: <44A8D54A.3000100@xxxxxxxxxx>
List-help: <mailto:xen-devel-request@lists.xensource.com?subject=help>
List-id: Xen developer discussion <xen-devel.lists.xensource.com>
List-post: <mailto:xen-devel@lists.xensource.com>
List-subscribe: <http://lists.xensource.com/cgi-bin/mailman/listinfo/xen-devel>, <mailto:xen-devel-request@lists.xensource.com?subject=subscribe>
List-unsubscribe: <http://lists.xensource.com/cgi-bin/mailman/listinfo/xen-devel>, <mailto:xen-devel-request@lists.xensource.com?subject=unsubscribe>
References: <44A8D54A.3000100@xxxxxxxxxx>
Sender: xen-devel-bounces@xxxxxxxxxxxxxxxxxxx

On 3 Jul 2006, at 09:28, 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!

You might want to try removing the call to pmtimer_init() in ioemu/hw/piix4acpi.c -- the pmtimer emulation is rather broken (burns 25% of a 3GHz cpu). I've just done this in xen-unstable.

 -- Keir

Xen-devel mailing list