From: Anthony Liguori <anthony@codemonkey.ws>
To: deshantm@gmail.com
Cc: "dan.magenheimer@oracle.com" <dan.magenheimer@oracle.com>,
"Xen-Devel (E-mail)" <xen-devel@lists.xensource.com>
Subject: Re: Xen performance and Dbench
Date: Thu, 07 Aug 2008 14:49:50 -0500 [thread overview]
Message-ID: <489B51DE.5020900@codemonkey.ws> (raw)
In-Reply-To: <1e16a9ed0808071210u4a18ada1i54507ebdab7057a7@mail.gmail.com>
Todd Deshane wrote:
> dbench is an interesting test since it is basically an I/O test (Samba test)
> http://samba.org/ftp/tridge/dbench/README
dbench is actually *not* an I/O test. It mostly stresses a filesystems
interaction with the page cache. It's heavily threaded and tends to
scale okay but it's rarely impacted heavily by the underlying storage
systems I/O performance. It tends to demonstrate shadow page table SMP
scalability more than I/O performance.
The OLS paper referenced really had bad methodologies. If you read
carefully, their host system was a 2-way system. They ran all of the
guests UP though. Since they didn't do a parallel make, it wasn't very
obvious for their "kernel build" but it became obvious with dbench since
there were multiple threads.
So native and "VServer" had access to both CPU cores whereas Xen, KVM,
et al were only running on a single core. There's no way dbench is 30%
of native under Xen. That should have been a big red flag that
something was wrong.
Regards,
Anthony Liguori
> I don't know if dbench is the best test to determine if Xen (or other
> virts) need
> to be fixed.
>
> Cheers,
> Todd
>
>
>> ===================================
>> Thanks... for the memory
>> I really could use more / My throughput's on the floor
>> The balloon is flat / My swap disk's fat / I've OOM's in store
>> Overcommitted so much
>> (with apologies to the late great Bob Hope)
>> _______________________________________________
>> Xen-devel mailing list
>> Xen-devel@lists.xensource.com
>> http://lists.xensource.com/xen-devel
>>
>>
>
>
>
next prev parent reply other threads:[~2008-08-07 19:49 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-08-07 17:18 Xen performance and Dbench Dan Magenheimer
2008-08-07 19:10 ` Todd Deshane
2008-08-07 19:49 ` Anthony Liguori [this message]
2008-08-07 22:23 ` Dan Magenheimer
2008-08-07 22:55 ` Todd Deshane
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=489B51DE.5020900@codemonkey.ws \
--to=anthony@codemonkey.ws \
--cc=dan.magenheimer@oracle.com \
--cc=deshantm@gmail.com \
--cc=xen-devel@lists.xensource.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.