coLinux benchmarks

[Dan Aloni]

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@xxxxxxxxxxx
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@xxxxxxxxxxxxxxx
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/