From: Keir Fraser <keir@xensource.com>
To: pak333@comcast.net, xen-devel@lists.xensource.com
Subject: Re: Credit scheduler
Date: Wed, 27 Jun 2007 02:17:32 +0100 [thread overview]
Message-ID: <C2A7793C.11612%keir@xensource.com> (raw)
In-Reply-To: <062720070109.4497.4681B8BB000E2A1E000011912207001641CCCCCC050E9F@comcast.net>
[-- Attachment #1.1: Type: text/plain, Size: 1909 bytes --]
Are these all Windows HVM guests? And do you exclude domain0 when you count
the number of VMs in your system (so it¹s actually 4 user VMs + domain0 VM)?
How did you come up with the 3us figure some kind of in-guest tracing, or
using xentrace, or by some other means?
Does the problem still happen if you run 2 cpu-intensive VMs instead of 3?
-- Keir
On 27/6/07 02:09, "pak333@comcast.net" <pak333@comcast.net> wrote:
>
> I have 4 physical cpus (2 dual core sockets) and the IO workload is loadsim
> with 500 users
>
> Thanks
> -Prabha
>
>
> -------------- Original message ----------------------
> From: Keir Fraser <keir@xensource.com>
>> > How many physical CPUs do you have, and what is the IO workload that one of
>> > the VMs is running?
>> >
>> > -- Keir
>> >
>> > On 26/6/07 22:33, "pak333@comcast.net" <pak333@comcast.net> wrote:
>> >
>>> > > Hi
>>> > >
>>> > > I have noticed that VMs are typically spending 3 microsecs or less
>>> before they
>>> > > are being prempted. I thought that the credit schduler time slice was 30
>>> ms. I
>>> > > have 4 VMs running and they are all cpu intensive except for 1 (which is
IO
>>> > > intensive) but having a VM spend max 3 micro secs before being kicked
out
>>> > > seems strange.
>>> > >
>>> > > Is there something else going on that i am not aware of. Is the time >>>
slice
>>> > > really 30 millisecs? I am using default parameters of the credit
>>> scheduler.
>>> > >
>>> > > Thanks
>>> > > -Prabha
>>> > >
>>> > >
>>> > >
>>> > > _______________________________________________
>>> > > Xen-devel mailing list
>>> > > Xen-devel@lists.xensource.com
>>> > > http://lists.xensource.com/xen-devel
>> >
>> >
>
>
>
> _______________________________________________
> Xen-devel mailing list
> Xen-devel@lists.xensource.com
> http://lists.xensource.com/xen-devel
[-- Attachment #1.2: Type: text/html, Size: 2735 bytes --]
[-- Attachment #2: Type: text/plain, Size: 138 bytes --]
_______________________________________________
Xen-devel mailing list
Xen-devel@lists.xensource.com
http://lists.xensource.com/xen-devel
next prev parent reply other threads:[~2007-06-27 1:17 UTC|newest]
Thread overview: 28+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-06-27 1:09 Credit scheduler pak333
2007-06-27 1:17 ` Keir Fraser [this message]
-- strict thread matches above, loose matches on Subject: below --
2015-10-21 18:03 Lasya Venneti
2015-10-22 11:28 ` Dario Faggioli
2011-09-18 15:21 credit scheduler Pratik shinde
2011-09-19 15:53 ` George Dunlap
2011-06-17 14:48 David Xu
2011-06-21 14:04 ` George Dunlap
2009-06-04 17:38 Credit Scheduler gaurav somani
2009-06-23 7:56 ` Michael xin
2007-07-12 23:21 Credit scheduler pak333
2007-07-13 7:30 ` Atsushi SAKAI
2007-07-13 18:11 ` Mats Petersson
2007-07-12 20:46 pak333
[not found] ` <071220072046.7704.4696931E000C3BAA00001E182207020953CCCCCC 050E9F@comcast.net>
2007-07-12 21:25 ` Mats Petersson
2007-06-27 5:15 pak333
2007-06-27 5:51 ` Atsushi SAKAI
2007-06-27 1:55 pak333
2007-06-27 11:04 ` Keir Fraser
2007-06-26 21:33 pak333
2007-06-27 0:59 ` Keir Fraser
2007-06-27 2:29 ` Atsushi SAKAI
2006-08-28 23:04 credit scheduler Ian Pratt
2006-08-28 22:28 Karl Rister
2006-08-29 6:16 ` Keir Fraser
2006-08-29 12:45 ` George Dunlap
2006-08-29 21:26 ` Sean Dague
2006-08-29 22:17 ` Emmanuel Ackaouy
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=C2A7793C.11612%keir@xensource.com \
--to=keir@xensource.com \
--cc=pak333@comcast.net \
--cc=xen-devel@lists.xensource.com \
/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.