All of lore.kernel.org
 help / color / mirror / Atom feed
From: Avi Kivity <avi@redhat.com>
To: Xupeng Yun <recordus@gmail.com>
Cc: kvm@vger.kernel.org
Subject: Re: High latency with VirtIO NIC
Date: Thu, 24 Mar 2011 16:08:04 +0200	[thread overview]
Message-ID: <4D8B5044.1050303@redhat.com> (raw)
In-Reply-To: <76F180B5B89249CDA99A9521558BAF11@gmail.com>

On 03/24/2011 03:45 PM, Xupeng Yun wrote:
> On Thursday, March 24, 2011 at 6:22 PM, Avi Kivity wrote:
> Try vhost-net, that should have much better latencies.
> >   Indeed, the latency is much better after switching to vhost-net, it drops from 3+ms to ~1.5ms on average
> when there is no network load on the KVM guest, but the latencies become bad again when there is
> heavy network load on the guest(~70Mbps RX and ~25Mbps TX).
>
> --------------------------- ping KVM guest (app211) from the host ---------------------------
> 64 bytes from app211 (192.168.1.211): icmp_seq=3582 ttl=64 time=3.08 ms
> 64 bytes from app211 (192.168.1.211): icmp_seq=3583 ttl=64 time=1.10 ms
> 64 bytes from app211 (192.168.1.211): icmp_seq=3584 ttl=64 time=1.03 ms
> 64 bytes from app211 (192.168.1.211): icmp_seq=3585 ttl=64 time=3.55 ms
> 64 bytes from app211 (192.168.1.211): icmp_seq=3586 ttl=64 time=1.29 ms
> 64 bytes from app211 (192.168.1.211): icmp_seq=3587 ttl=64 time=0.710 ms
> 64 bytes from app211 (192.168.1.211): icmp_seq=3588 ttl=64 time=64.4 ms
> 64 bytes from app211 (192.168.1.211): icmp_seq=3589 ttl=64 time=0.271 ms
> 64 bytes from app211 (192.168.1.211): icmp_seq=3590 ttl=64 time=0.563 ms
> 64 bytes from app211 (192.168.1.211): icmp_seq=3591 ttl=64 time=1.66 ms
> 64 bytes from app211 (192.168.1.211): icmp_seq=3592 ttl=64 time=0.939 ms
> 64 bytes from app211 (192.168.1.211): icmp_seq=3593 ttl=64 time=0.819 ms
> 64 bytes from app211 (192.168.1.211): icmp_seq=3594 ttl=64 time=16.5 ms
>
> --------------------------- ping KVM guest (app211) from the host ---------------------------
>
> any idea?
>

Isn't it normal?  With heavy load, packets start to queue.

-- 
error compiling committee.c: too many arguments to function


  parent reply	other threads:[~2011-03-24 14:08 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2011-03-24  0:37 High latency with VirtIO NIC Xupeng Yun
2011-03-24 10:22 ` Avi Kivity
2011-03-24 13:45   ` Xupeng Yun
2011-03-24 13:50     ` Xupeng Yun
2011-03-24 14:08     ` Avi Kivity [this message]
2011-03-24 14:24       ` Xupeng Yun
2011-03-24 14:27         ` Avi Kivity
2011-03-24 14:34           ` Xupeng Yun

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=4D8B5044.1050303@redhat.com \
    --to=avi@redhat.com \
    --cc=kvm@vger.kernel.org \
    --cc=recordus@gmail.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.