[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: [Xen-devel] Re: [Xen-users] About profiling xen

  • To: Pasi Kärkkäinen <pasik@xxxxxx>, Marco Tizzoni <marco.tizzoni@xxxxxxxxx>
  • From: Fasiha Ashraf <feehapk@xxxxxxxxxxx>
  • Date: Tue, 6 Oct 2009 12:52:36 +0530 (IST)
  • Cc: "Fajar A." <fajar@xxxxxxxxx>, xen <xen-devel@xxxxxxxxxxxxxxxxxxx>, xen-users@xxxxxxxxxxxxxxxxxxx
  • Delivery-date: Tue, 06 Oct 2009 00:23:27 -0700
  • Domainkey-signature: a=rsa-sha1; q=dns; c=nofws; s=s1024; d=yahoo.co.in; h=Message-ID:X-YMail-OSG:Received:X-Mailer:Date:From:Subject:To:Cc:In-Reply-To:MIME-Version:Content-Type; b=jdrq3bWrC8kVwZsF/wn4pg9vTcPXiM7f4rY7ZVPPboEpX9dNvdYrfU0ASdwZXnG4zK/zU3dpRDADKpIMOfRFxj9V9D+oo6Be8e8BSH2Cmb1nT8gd4gukXPGXE3gP2tdfwEls5qjCzPhgNiVNXxcs1/vu/eRUOMciPa9NecCfOko=;
  • List-id: Xen user discussion <xen-users.lists.xensource.com>

Is this guest to guest throuput issue resolved? 
What  is affecting guest to guest throughput? Since I have timer frequency 1000Hz and high resolution timer both enabled in my dom0. Also i am using cpu cores pinned for each VM an Dom0. Please guide me some more about getting increased throughput between guests.
Fasiha Ashraf

--- On Wed, 30/9/09, Marco Tizzoni <marco.tizzoni@xxxxxxxxx> wrote:

From: Marco Tizzoni <marco.tizzoni@xxxxxxxxx>
Subject: Re: [Xen-devel] Re: [Xen-users] About profiling xen
To: "Pasi Kärkkäinen" <pasik@xxxxxx>
Cc: "Fajar A." <fajar@xxxxxxxxx>, "Fasiha Ashraf" <feehapk@xxxxxxxxxxx>, "xen" <xen-devel@xxxxxxxxxxxxxxxxxxx>, xen-users@xxxxxxxxxxxxxxxxxxx
Date: Wednesday, 30 September, 2009, 11:40 AM

On Wed, Sep 30, 2009 at 8:37 AM, Pasi Kärkkäinen <pasik@xxxxxx> wrote:
> On Wed, Sep 30, 2009 at 08:33:19AM +0200, Marco Tizzoni wrote:
>>    I experienced the same problem with netperf and with hping also. In
>>    general every tool that sends packet at fixed rates seems to suffer this
>>    problem. If you use the flood option ( sends packets as fast as possible -
>>    for example 'ping -f' or 'hping3 -f') instead of a fixed rate the rate
>>    become much higher. What I discovered is this issue should be related to
>>    Xen's signal handling/delivery.
>>    Netperf use setitimer() to send packets at fixed rate. In my experience on
>>    dom0/U, with no load, Xen cannot go over 250 signals per second. Because
>>    netperf use signal wakeup the function that send packets I think your
>>    problem can be related to this issue. If you want to be sure, count the
>>    average number of packet per seconds. It should be about 250 packets/s
>>    (not more).
> 250 per second.. sounds like kernel HZ value?

Yes, infact I'm going to test it with 1000Khz. Stay tuned.



Xen-devel mailing list

Keep up with people you care about with Yahoo! India Mail. Learn how.
Xen-users mailing list



Lists.xenproject.org is hosted with RackSpace, monitoring our
servers 24x7x365 and backed by RackSpace's Fanatical Support®.