From: Stefan Hajnoczi <stefanha@gmail.com>
To: Alejandro Comisario <alejandro.comisario@mercadolibre.com>
Cc: kvm@vger.kernel.org, linux-kernel@vger.kernel.org,
"Michael S. Tsirkin" <mst@redhat.com>,
jasowang@redhat.com
Subject: Re: kvm virtio ethernet ring on guest side over high throughput (packet per second)
Date: Wed, 22 Jan 2014 09:22:39 -0600 [thread overview]
Message-ID: <20140122152239.GA11404@stefanha-thinkpad.redhat.com> (raw)
In-Reply-To: <CAMrG31x0H1OjtNfdcXq2EqZ20XPHCX8qvrQSSuMqR=hsttYmXQ@mail.gmail.com>
On Tue, Jan 21, 2014 at 04:06:05PM -0200, Alejandro Comisario wrote:
CCed Michael Tsirkin and Jason Wang who work on KVM networking.
> Hi guys, we had in the past when using physical servers, several
> throughput issues regarding the throughput of our APIS, in our case we
> measure this with packets per seconds, since we dont have that much
> bandwidth (Mb/s) since our apis respond lots of packets very small
> ones (maximum response of 3.5k and avg response of 1.5k), when we
> where using this physical servers, when we reach throughput capacity
> (due to clients tiemouts) we touched the ethernet ring configuration
> and we made the problem dissapear.
>
> Today with kvm and over 10k virtual instances, when we want to
> increase the throughput of KVM instances, we bumped with the fact that
> when using virtio on guests, we have a max configuration of the ring
> of 256 TX/RX, and from the host side the atached vnet has a txqueuelen
> of 500.
>
> What i want to know is, how can i tune the guest to support more
> packets per seccond if i know that's my bottleneck?
I suggest investigating performance in a systematic way. Set up a
benchmark that saturates the network. Post the details of the benchmark
and the results that you are seeing.
Then, we can discuss how to investigate the root cause of the bottleneck.
> * does virtio exposes more packets to configure in the virtual ethernet's ring ?
No, ring size is hardcoded in QEMU (on the host).
> * does the use of vhost_net helps me with increasing packets per
> second and not only bandwidth?
vhost_net is generally the most performant network option.
> does anyone has to struggle with this before and knows where i can look into ?
> there's LOOOOOOOOOOOOOOOTS of information about networking performance
> tuning of kvm, but nothing related to increase throughput in pps
> capacity.
>
> This is a couple of configurations that we are having right now on the
> compute nodes:
>
> * 2x1Gb bonded interfaces (want to know the more than 20 models we are
> using, just ask for it)
> * Multi queue interfaces, pined via irq to different cores
> * Linux bridges, no VLAN, no open-vswitch
> * ubuntu 12.04 kernel 3.2.0-[40-48]
next prev parent reply other threads:[~2014-01-22 15:22 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-01-21 18:06 Alejandro Comisario
2014-01-22 15:22 ` Stefan Hajnoczi [this message]
2014-01-22 21:32 ` Alejandro Comisario
2014-01-23 3:14 ` Jason Wang
2014-01-23 19:25 ` Alejandro Comisario
2014-01-24 18:40 ` Alejandro Comisario
2014-01-23 3:12 ` Jason Wang
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=20140122152239.GA11404@stefanha-thinkpad.redhat.com \
--to=stefanha@gmail.com \
--cc=alejandro.comisario@mercadolibre.com \
--cc=jasowang@redhat.com \
--cc=kvm@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=mst@redhat.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox
all inboxes | Powered by JetHome®