All of lore.kernel.org
 help / color / mirror / Atom feed
From: Avi Kivity <avi-atKUWr5tajBWk0Htik3J/w@public.gmane.org>
To: Benjamin Prosnitz <b-prosnitz-angj7XTnwNpXfO9P/gJGhg@public.gmane.org>
Cc: kvm-devel-5NWGOfrQmneRv+LV9MX5uipxlwaOVQ5f@public.gmane.org
Subject: Re: Floating point vs Integer performance
Date: Tue, 13 Mar 2007 10:03:20 +0200	[thread overview]
Message-ID: <45F65AC8.2000605@qumranet.com> (raw)
In-Reply-To: <1173730724.7220.5.camel@localhost>

Benjamin Prosnitz wrote:
> I ran some benchmarks inside of KVM-12 on my system and outside of KVM
> (no virtualization on my system).  I found that floating point
> performance when running both with and without KVM was approximately the
> same, but integer performance in KVM was about 25% of what I get when
> running the test outside of KVM. These were tests using Dhrystone 2 and
> Double Precision Whetstone on a Core 2 Duo T7200 processor.
>
> Any thoughts on why the integer and floating point performance appears
> to differ so much?
>
>   

Perhaps the integer benchmarks thrash the mmu cache.  Try raising 
KVM_NUM_MMU_PAGES to 1024.

4MB per VM lowmem is a lot, but if it helps many workloads, it's worth it.


-- 
Do not meddle in the internals of kernels, for they are subtle and quick to panic.


-------------------------------------------------------------------------
Take Surveys. Earn Cash. Influence the Future of IT
Join SourceForge.net's Techsay panel and you'll get the chance to share your
opinions on IT & business topics through brief surveys-and earn cash
http://www.techsay.com/default.php?page=join.php&p=sourceforge&CID=DEVDEV

  reply	other threads:[~2007-03-13  8:03 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2007-03-12 20:18 Floating point vs Integer performance Benjamin Prosnitz
2007-03-13  8:03 ` Avi Kivity [this message]
2007-03-13  8:16 ` Michael Riepe

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=45F65AC8.2000605@qumranet.com \
    --to=avi-atkuwr5tajbwk0htik3j/w@public.gmane.org \
    --cc=b-prosnitz-angj7XTnwNpXfO9P/gJGhg@public.gmane.org \
    --cc=kvm-devel-5NWGOfrQmneRv+LV9MX5uipxlwaOVQ5f@public.gmane.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 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.