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


[Xen-devel] SEDF regression

To: xen-devel <xen-devel@xxxxxxxxxxxxxxxxxxx>
Subject: [Xen-devel] SEDF regression
From: "Diwaker Gupta" <diwaker.lists@xxxxxxxxx>
Date: Thu, 27 Jul 2006 18:09:44 -0700
Delivery-date: Thu, 27 Jul 2006 18:10:05 -0700
Domainkey-signature: a=rsa-sha1; q=dns; c=nofws; s=beta; d=gmail.com; h=received:message-id:date:from:to:subject:mime-version:content-type:content-transfer-encoding:content-disposition; b=K/H6W5Kug2K9jSDG1mmEQwrCMV/N/Y+6w/mcNu5z/HCM+lx2bSTV7s3pLnwH9shJLtOxS8vp7GS211ujvlfCaoLtbKd4K7AxUj5rtFKgo6EudbwXqYa1YnKuGc7G0YNAvsKazhCFlqmTk65L/jbsTQ5Xt3WKGj/6GBa+C0VGjIM=
Envelope-to: www-data@xxxxxxxxxxxxxxxxxx
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>
Sender: xen-devel-bounces@xxxxxxxxxxxxxxxxxxx
I know that SEDF is not the default scheduler anymore, but I still
wanted to bring this to attention if some folks are continuing with
SEDF. I've been doing benchmarking with SEDF with very simple web
workloads, and I'm seeing some very strange behavior that was not
present before.

The setup is as follows: I have a single VM (nosmp) apart from dom0
(nosmp). The VM runs a web server which is loaded using httperf from
another machine. I'm measuring web server throughput as a function of
the relative weights of domain-0 and domain-1.

I get a through of around 1200 req/s with the following slice/period
dom0: 3ms out of 10ms
dom1: 7ms out of 10ms

But, with only around 600 req/s with the following:
dom0: 30ms out of 100ms
dom1: 70ms out of 100ms

In both cases, the extra time flag is set to 0 and the latency hint is
also set to 0.

Thats half the throughput with a roughly equivalent set of weights. I
haven't isolated the exact changeset that might be the culprit, but
until about a few months back, this didn't happen. If anyone has seen
similar behavior, please let me know -- I'd be really interested in
hearing about it.

Web/Blog/Gallery: http://floatingsun.net/blog

Xen-devel mailing list

<Prev in Thread] Current Thread [Next in Thread>
  • [Xen-devel] SEDF regression, Diwaker Gupta <=