From mboxrd@z Thu Jan 1 00:00:00 1970 Received: from eggs.gnu.org ([208.118.235.92]:40338) by lists.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1SzRhm-0003qJ-Ur for qemu-devel@nongnu.org; Thu, 09 Aug 2012 08:19:11 -0400 Received: from Debian-exim by eggs.gnu.org with spam-scanned (Exim 4.71) (envelope-from ) id 1SzRhl-0008Py-Uo for qemu-devel@nongnu.org; Thu, 09 Aug 2012 08:19:10 -0400 Received: from mx1.redhat.com ([209.132.183.28]:7715) by eggs.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1SzRhl-0008Po-N4 for qemu-devel@nongnu.org; Thu, 09 Aug 2012 08:19:09 -0400 Message-ID: <5023AAB8.1090703@redhat.com> Date: Thu, 09 Aug 2012 14:19:04 +0200 From: Paolo Bonzini MIME-Version: 1.0 References: <502283FA.2080506@profihost.ag> <5022912B.2000607@redhat.com> <50235527.4090804@profihost.ag> <50236059.7060801@redhat.com> <4A799203-5BFF-4DE9-9B85-459096EBEC22@profihost.ag> <50236484.2090702@redhat.com> <502369C7.7000300@profihost.ag> <50238E2A.1050203@profihost.ag> <5023A83D.9070509@profihost.ag> In-Reply-To: <5023A83D.9070509@profihost.ag> Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: 7bit Subject: Re: [Qemu-devel] virtio-scsi vs. virtio-blk List-Id: List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , To: Stefan Priebe - Profihost AG Cc: Stefan Hajnoczi , qemu-devel Il 09/08/2012 14:08, Stefan Priebe - Profihost AG ha scritto: > > virtio-scsi: > rand 4k: > write: io=822448KB, bw=82228KB/s, iops=20557, runt= 10002msec > read : io=950920KB, bw=94694KB/s, iops=23673, runt= 10042msec > seq: > write: io=2436MB, bw=231312KB/s, iops=56, runt= 10784msec > read : io=3248MB, bw=313799KB/s, iops=76, runt= 10599msec > > virtio-blk: > rand 4k: > write: io=896472KB, bw=89051KB/s, iops=22262, runt= 10067msec > read : io=1710MB, bw=175073KB/s, iops=43768, runt= 10002msec > seq: > write: io=4008MB, bw=391285KB/s, iops=95, runt= 10489msec > read : io=5748MB, bw=570178KB/s, iops=139, runt= 10323msec Thanks; some overhead is expected, but not this much. Especially the sequential case is bad, what disk is this? Things to test include: - using the deadline I/O scheduler on at least the host, and possibly the guest too - running perf on the guest and the host (separately) to get profiles Paolo