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

Re: [Xen-devel] n/w performance degradation


  • To: Ian Pratt <m+Ian.Pratt@xxxxxxxxxxxx>
  • From: Diwaker Gupta <diwaker.lists@xxxxxxxxx>
  • Date: Mon, 5 Dec 2005 16:06:52 -0800
  • Cc: xen-devel@xxxxxxxxxxxxxxxxxxx
  • Delivery-date: Tue, 06 Dec 2005 00:07:13 +0000
  • Domainkey-signature: a=rsa-sha1; q=dns; c=nofws; s=beta; d=gmail.com; h=received:message-id:date:from:to:subject:cc:in-reply-to:mime-version:content-type:content-transfer-encoding:content-disposition:references; b=NycDztLPfH86JR+LaLubok0jiwAIzc64sFTsaKQ31/BHT2oKliF8+9lsc8SPconFeVEwUhpR92lNMuEYOBdDWgtpVX/UwaBccoBozY+WcHKpNYt7MOf+G7HvYy311cCkukRPchYqmK09hJp4hVK5sQtBUMIK64E9NeaMO+IMu3U=
  • List-id: Xen developer discussion <xen-devel.lists.xensource.com>

> The main focus of the 3.0.0 release has been corectness rather than
> performance tuning. We plan to do some tweaking over the coming weeks to
> address this. We used to get 900Mb/s with a single CPU core, and there's
> absoloutely no reason why we shouldn't do so again -- in fact, we should
> do better in terms of CPU usage than 2.0 as as we now have checksum
> offload.

I completely agree. Now that 3.0.0 is out of the door, it should be
easier to focus on performance, rather than functionality and
correctness.

> Now we have great performance monitoring tools like xen-oprofile,
> xenperf, xenmon etc it should be wuite straightforward to optimize
> things.  Let's just wait until we've delt with any critical bugs arising
> from the release...

Sounds good, thanks.

Diwaker
--
Web/Blog/Gallery: http://floatingsun.net
_______________________________________________
Xen-devel mailing list
Xen-devel@xxxxxxxxxxxxxxxxxxx
http://lists.xensource.com/xen-devel

 


Rackspace

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