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

[Xen-API] delays with network traffic


  • To: xen-api@xxxxxxxxxxxxxxxxxxx
  • From: George Shuklin <george.shuklin@xxxxxxxxx>
  • Date: Mon, 25 Apr 2011 19:31:20 +0400
  • Delivery-date: Mon, 25 Apr 2011 08:31:41 -0700
  • Domainkey-signature: a=rsa-sha1; c=nofws; d=gmail.com; s=gamma; h=subject:from:to:content-type:date:message-id:mime-version:x-mailer :content-transfer-encoding; b=LlD3XvP78rIzJK2XWRR0OJAlOMAXozNmtSL6yDSTQlxM2mkBq/3vvBsIXbED/j8fsm AOYxtZQZJ15zmWJaEo4/NDks6C0XzbA0advU/3tS9XF6p1nyLrDrsuxuiBDZ+aa89e3w MKU/NUaO7v/gd45UQb9lsF1psjSWwLUsDG2w4=
  • List-id: Discussion of API issues surrounding Xen <xen-api.lists.xensource.com>

Good day.

Found strange behavior with xapi and guest network traffic. If we starts
to ping domU with high speed (about 3-4 pings per second) and do some
operations with xapi (f.e. xe vm-list, etc) we can see delays in pings
(up to 80 ms compare to usual 0.3-0.8). All guest are PVs.

I dig pretty much about this and found:

1) raising nice number for xenstored (nice 10, nice 20) make delays
lower.
2) Pinning dom0 and adding VCPU to dom0 slightly helps, but not
significantly. 
3) switching to bridge instead ovs makes things worse (but not really
much).
4) CPU load in domU does not change behavior (not better, not worse)
5) High network and disk activity for domU make it replays sometimes
longer (up to 100ms with average load < 0.5)

In some tests I was able to get ping about 5-6ms instead 0.3-0.8 just by
running python (without options).

I feel I miss something or do not understand.

---
wBR, George.



_______________________________________________
xen-api mailing list
xen-api@xxxxxxxxxxxxxxxxxxx
http://lists.xensource.com/mailman/listinfo/xen-api


 


Rackspace

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