All of lore.kernel.org
 help / color / mirror / Atom feed
From: Dan Aloni <da-x@colinux.org>
To: Cooperative Linux Development  <colinux-devel@lists.sourceforge.net>
Cc: Linux Kernel List <linux-kernel@vger.kernel.org>
Subject: coLinux benchmarks
Date: Mon, 5 Apr 2004 15:15:20 +0200	[thread overview]
Message-ID: <20040405131520.GA4395@callisto.yi.org> (raw)

Hello,

Today I ran some dbench2 benchmarks in order to test coLinux's
(http://www.colinux.org) virtual disk I/O performance.

I'm cross-posting this message to the LKML, as I know that on that
list there are some benchmarking experts or other people who may 
find this interesting.

This is the output from a coLinux 2.4.25 guest VM configured with 
128MB RAM running on a Linux 2.6.3 (BK) host that has a total of 
256MB RAM. The host machine has a Mobile Intel Celeron CPU (2.20GHz). 
All filesystems used are ext3.

    colinux:/home/dax# dbench 5 -s -S
    5 clients started
       0     62477  10.01 MB/sec
    Throughput 10.0026 MB/sec (sync open) (sync dirs) 5 procs

    colinux:/home/dax# dbench 5 -s -S
    5 clients started
       0     62477  10.43 MB/sec
    Throughput 10.4262 MB/sec (sync open) (sync dirs) 5 procs

    colinux:/home/dax# dbench 5 -s -S
    5 clients started
       0     62477  10.90 MB/sec
    Throughput 10.8926 MB/sec (sync open) (sync dirs) 5 procs


I then ran the same thing on the host itself, *without* the 
coLinux VM running in the background:

    hostile17:~/colinux# dbench 5 -s -S
    5 clients started
       0     62477  5.08 MB/sec
    Throughput 5.07573 MB/sec (sync open) (sync dirs) 5 procs
    
    hostile17:~/colinux# dbench 5 -s -S
    5 clients started
       0     62477  5.13 MB/sec
    Throughput 5.12705 MB/sec (sync open) (sync dirs) 5 procs


The VM shows better results than the host. What gives? Perhaps
it is because of the combination of the host and guest's buffer 
cache? I'd like to know about more percise benchmarking methods 
for VMs.

-- 
Dan Aloni
Cooperative Linux, lead developer
da-x@colinux.org

             reply	other threads:[~2004-04-05 13:14 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2004-04-05 13:15 Dan Aloni [this message]
2004-04-05 13:30 ` coLinux benchmarks Christoph Hellwig
2004-04-05 14:05   ` Dan Aloni
2004-04-05 20:11 ` [coLinux-devel] " Eyal Lotem
2004-04-05 22:22   ` Dan Aloni
2004-04-06 13:45     ` Ian C. Blenke
2004-04-06 14:07       ` Dan Aloni
2004-04-05 23:21 ` ReactOS and CoLinux status Steven Edwards

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=20040405131520.GA4395@callisto.yi.org \
    --to=da-x@colinux.org \
    --cc=colinux-devel@lists.sourceforge.net \
    --cc=linux-kernel@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 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.