qemu-devel.nongnu.org archive mirror
 help / color / mirror / Atom feed
From: Erik Rull <erik.rull@rdsoftware.de>
To: Alex Williamson <alex.williamson@redhat.com>
Cc: qemu-devel@nongnu.org
Subject: Re: [Qemu-devel] Enabling Hyperthreading for Guest
Date: Fri, 23 Sep 2011 17:29:44 +0200	[thread overview]
Message-ID: <4E7CA5E8.7030304@rdsoftware.de> (raw)
In-Reply-To: <1316711751.25092.6.camel@x201.home>

Alex Williamson wrote:
> On Thu, 2011-09-22 at 18:43 +0200, Erik Rull wrote:
>> Alex Williamson wrote:
>>> See the extended -smp options:
>>>
>>> -smp n[,maxcpus=cpus][,cores=cores][,threads=threads][,sockets=sockets]
>>>                   set the number of CPUs to 'n' [default=1]
>>>                   maxcpus= maximum number of total cpus, including
>>>                   offline CPUs for hotplug, etc
>>>                   cores= number of CPU cores on one socket
>>>                   threads= number of threads on one CPU core
>>>                   sockets= number of discrete sockets in the system
>>>
>>> Try something like:
>>>
>>> -smp 4,cores=2,threads=2,sockets=1
>>>
>>> Alex
>>>
>>
>> Great - the correct combination made it :-)
>>
>> But the SMP-Performance-Benchmark is horrible :-(
>> "Only" between 0.35 and 1.05 for the above combination.
>
> I'm not sure what that means...
>
>> I have the same architecture on the host (2 cores w/ ht enabled) so there
>> are enough real cores available for computation.
>>
>> Any idea what could slow down the performance here?
>
> Note that threads aren't real "full" cores, so you're likely going to
> see some scheduling mismatches between physical threads and virtual
> threads.  One thing that often helps smp guests is to pin vCPUs to
> pCPUs.  You can get the vCPU thread IDs from 'info cpu' in the monitor
> and pin each to a physical CPU with taskset.  If you're using libvirt,
> virt-manager can configure it to do this too (as well as the cpu
> topology).
>
> Alex
>

The SMP factor means how much speed improvement was gained using SMP 
against a single core with the same algorithm. My results showed a heavy 
performance breakdown when doing the SMP benchmark.
Fixing the virtual cores to the physical ones worked with taskset but 
didn't bring that real performance improvements at all :-(

Maybe the used algorithm for benchmarking is not the best one, I will try 
others.

Best regards,

Erik

  reply	other threads:[~2011-09-23 15:29 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2011-09-21 13:02 [Qemu-devel] Enabling Hyperthreading for Guest erik.rull
2011-09-21 20:02 ` Alex Williamson
2011-09-22 16:43   ` Erik Rull
2011-09-22 17:15     ` Alex Williamson
2011-09-23 15:29       ` Erik Rull [this message]
2011-09-23 16:49         ` Alex Williamson

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=4E7CA5E8.7030304@rdsoftware.de \
    --to=erik.rull@rdsoftware.de \
    --cc=alex.williamson@redhat.com \
    --cc=qemu-devel@nongnu.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).