From mboxrd@z Thu Jan 1 00:00:00 1970 From: "Henrik Holst" Subject: Re: Disk Benchmark results, kvm-69 Date: Mon, 21 Jul 2008 23:31:38 +0200 Message-ID: <4e9085270807211431o5115cadds2c4d47b095d9629b@mail.gmail.com> References: <1211799364.5779.25.camel@henrik-desktop> Mime-Version: 1.0 Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: 7bit To: kvm@vger.kernel.org Return-path: Received: from yw-out-2324.google.com ([74.125.46.31]:34914 "EHLO yw-out-2324.google.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1751610AbYGUVbj (ORCPT ); Mon, 21 Jul 2008 17:31:39 -0400 Received: by yw-out-2324.google.com with SMTP id 9so615886ywe.1 for ; Mon, 21 Jul 2008 14:31:38 -0700 (PDT) In-Reply-To: <1211799364.5779.25.camel@henrik-desktop> Content-Disposition: inline Sender: kvm-owner@vger.kernel.org List-ID: 2008/5/26 Henrik Holst : > > We have performed some quick benchmarks against kvm-69 on an Intel Q6600 > with 8GB RAM and equipped with 4 SATA drives (Maxtor DiamondMax 10 > 6V300F0). > > During these tests we noticed a problem with the virtio block device in > where it completely locks the drive after a while when running on a smp > guest. The other disks are ok and the guest is working as it should but > all access to /dev/vda1 never times out. > > Also with if=scsi the host would output (during the bonnie++ tests): > lsi_scsi: error: PRDERED queue not implemented > lsi_scsi: error: Unimplemented message 0x0c > > Host: 2.6.24-1-amd64 debian testing > Guest: 2.6.24-16-server ubuntu 8.04 > > hdparm -tT /dev/sdb on host: > Timing cached reads: 3845.63 MB/sec > Timing buffered disk reads: 67.98 MB/sec > > Qemu invocation (for virtio): > qemu-system-x86_64 > -m 3072 -smp 4 \ > -drive file=ubuntu.img,if=ide,boot=on,media=disk \ > -drive file=/dev/sdb,if=virtio,boot=off,cache=off,media=disk > > Bonnie++ invocation: > bonnie++ -r 512 -s 2048 -u root -d /mnt/sdb1/ : > > Results: > --------------------------------------------------------------------------------- > Version 1.03b ------Sequential Output------ --Sequential Input- --Random- > -Per Chr- --Block-- -Rewrite- -Per Chr- --Block-- --Seeks-- > Machine Size K/sec %CP K/sec %CP K/sec %CP K/sec %CP K/sec %CP /sec %CP > host 2G 60814 81 83149 15 64419 8 85187 99 2394159 100 +++++ +++ > guest-ide 2G 65048 89 72621 13 64792 9 84224 99 2311183 99 +++++ +++ > guest-scsi 2G 67387 90 73757 13 63783 9 84645 100 2297687 99 +++++ +++ > guest-virtio 2G 41564 57 73274 28 62725 27 71656 85 2441544 98 +++++ +++ (This is with -smp 1) > > There seams to be no major performance difference between ide and scsi while virtio is not to be recommended at this moment. > All in all the IO looks very close to native, at least with this limited tests. > > /Henrik Holst > > I've just re-run this on kvm-71 and virtio seams to be corrected on smp systems now. We could find no lockups using virtio and 4 smp cores. Version 1.03b ------Sequential Output------ --Sequential Input- --Random- -Per Chr- --Block-- -Rewrite- -Per Chr- --Block-- --Seeks-- Machine Size K/sec %CP K/sec %CP K/sec %CP K/sec %CP K/sec %CP /sec %CP host 2G 60814 81 83149 15 64419 8 85187 99 2394159 100 +++++ +++ guest-ide 2G 65048 89 72621 13 64792 9 84224 99 2311183 99 +++++ +++ guest-virtio 2G 44011 68 92460 32 34272 9 38224 47 2277747 99 +++++ +++ Virtio block devices seams thus to be slower on putc and reads overall while faster on block writes. For some reason we couldn't manage to boot a scsi guest on the smp host, I'll get back with more info on this as soon as I have gathered some. /Henrik Holst