kvm.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Avi Kivity <avi@redhat.com>
To: "BRAUN, Stefanie" <Stefanie.Braun@alcatel-lucent.de>
Cc: kvm@vger.kernel.org
Subject: Re: KVM performance
Date: Mon, 06 Apr 2009 14:45:12 +0300	[thread overview]
Message-ID: <49D9EB48.4030709@redhat.com> (raw)
In-Reply-To: <133D9897FB9C5E4E9DF2779DC91E947C518348@SLFSNX.rcs.alcatel-research.de>

BRAUN, Stefanie wrote:
> Hallo,
>
> as I want to switch from XEN to KVM I've made some performance tests
> to see if KVM is as peformant as XEN. But tests with a VMU that receives
> a streamed video, adds a small logo to the video and streams it to a
> client
> have shown that XEN performs much betten than KVM. 
> In XEN the vlc (videolan client used to receive, process and send the
> video) process 
> within the vmu has a cpuload of 33,8 % whereas in KVM
> the vlc process has a cpuload of 99.9 %.
> I'am not sure why, does anybody now some settings to improve
> the KVM performance?
>   

Is this a tcp test?

Can you test receive and transmit separately?

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


  reply	other threads:[~2009-04-06 11:45 UTC|newest]

Thread overview: 29+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2009-04-03 11:32 KVM performance BRAUN, Stefanie
2009-04-06 11:45 ` Avi Kivity [this message]
     [not found]   ` <133D9897FB9C5E4E9DF2779DC91E947C51834A@SLFSNX.rcs.alcatel-research.de>
     [not found]     ` <49DA2F54.8090109@redhat.com>
2009-04-07 17:00       ` AW: AW: " BRAUN, Stefanie
2009-04-07 17:34         ` Avi Kivity
2009-04-08 11:38           ` AW: " BRAUN, Stefanie
2009-04-09 15:34             ` BRAUN, Stefanie
2009-04-11 16:19               ` Avi Kivity
2009-04-14  8:26                 ` AW: " BRAUN, Stefanie
2009-04-14  8:47                   ` Avi Kivity
2009-04-16 13:27                     ` AW: " BRAUN, Stefanie
2009-04-16 14:40                       ` Avi Kivity
2009-04-06 12:13 ` Hauke Hoffmann
2009-04-06 16:30   ` AW: " BRAUN, Stefanie
2009-04-07 12:58   ` BRAUN, Stefanie
  -- strict thread matches above, loose matches on Subject: below --
2008-11-14 18:35 Randy Broman
2008-11-14 18:58 ` David S. Ahern
2008-11-16 14:26 ` Avi Kivity
2008-11-16 22:08   ` Randy Broman
2008-11-17 14:50     ` Brian Jackson
2008-11-20 11:08     ` Avi Kivity
2007-01-27  0:21 Tim Chen
     [not found] ` <1169857267.30807.44.camel-bi+AKbBUZKY6gyzm1THtWbp2dZbC/Bob@public.gmane.org>
2007-01-27  3:11   ` Fabian Deutsch
2007-01-27  8:34   ` Avi Kivity
     [not found]     ` <45BB0E85.9060303-atKUWr5tajBWk0Htik3J/w@public.gmane.org>
2007-01-27 12:48       ` Rusty Russell
     [not found]         ` <1169902138.32208.25.camel-bi+AKbBUZKY6gyzm1THtWbp2dZbC/Bob@public.gmane.org>
2007-01-28  9:40           ` Avi Kivity
     [not found]             ` <45BC6F98.908-atKUWr5tajBWk0Htik3J/w@public.gmane.org>
2007-01-30 12:52               ` Rusty Russell
     [not found]                 ` <1170161536.17669.10.camel-bi+AKbBUZKY6gyzm1THtWbp2dZbC/Bob@public.gmane.org>
2007-01-30 12:56                   ` Avi Kivity
     [not found]                     ` <45BF4082.3010803-atKUWr5tajBWk0Htik3J/w@public.gmane.org>
2007-01-31  1:54                       ` Rusty Russell
2007-01-30 15:11                   ` Anthony Liguori

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=49D9EB48.4030709@redhat.com \
    --to=avi@redhat.com \
    --cc=Stefanie.Braun@alcatel-lucent.de \
    --cc=kvm@vger.kernel.org \
    /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;
as well as URLs for NNTP newsgroup(s).