qemu-devel.nongnu.org archive mirror
 help / color / mirror / Atom feed
From: Hao Xu <hao.xu@linux.dev>
To: Vivek Goyal <vgoyal@redhat.com>, Stefan Hajnoczi <stefanha@gmail.com>
Cc: qemu-devel <qemu-devel@nongnu.org>, virtio-fs@redhat.com
Subject: Re: Question about performance comparison between virtio-fs and virtio-blk
Date: Tue, 26 Jul 2022 22:41:23 +0800	[thread overview]
Message-ID: <1d1f7854-209a-a985-e266-633ca14609da@linux.dev> (raw)
In-Reply-To: <Yt/pVXilvkiLgowx@redhat.com>

On 7/26/22 21:17, Vivek Goyal wrote:
> On Tue, Jul 26, 2022 at 08:55:38AM -0400, Stefan Hajnoczi wrote:
>> On Tue, 26 Jul 2022 at 08:24, Hao Xu <hao.xu@linux.dev> wrote:
>>> I watched your presentation about virtiofs in 2020,
>>>
>>> https://www.youtube.com/watch?v=EIVOzTsGMMI&t=232s
>>>
>>> which is really helpful to me, but I have a question about the graph at
>>> 3:53, could you give
>>>
>>> me more info about the test, like what tool you use for the test, if
>>> it's fio, what is the parameters.
>>>
>>> I used fio to do randread test in a qemu box, but turns out the iops of
>>> virtio-blk and virtio-fs are similar.
>>
> 
> Hi Hao,
> 
> My impression in general is that virtio-blk is much faster than virtiofs.

When testing virtio-blk, did you use the device directly or mount it and
test against a file.

> A simple macro test is do a kernel compilation and compare time taken
> between the two.

Good idea, I just tested with single file.

Thanks,
Hao

> 
>> I have CCed Vivek Goyal, who has done more virtiofs benchmarking and
>> might have ideas to share.
>>
>> The benchmarking tool was fio with the stated blocksize and I/O
>> pattern. The benchmark was probably run with direct=1. Based on the
>> virtio-blk numbers I think iodepth was greater than 1 but I don't have
>> the exact fio job parameters.
> 
> I had basically used fio jobs. I wrote some simple wrapper scripts to
> run fio and parse and report numbers.
> 
> https://github.com/rhvgoyal/virtiofs-tests
> 
> I don't have data for virtio-blk but I do seem to have some comparison
> numbers of virtiofs and virtio-9p.
> 
> https://github.com/rhvgoyal/virtiofs-tests/tree/master/performance-results/feb-23-2021
> 
> Thanks
> Vivek
> 
> 



  reply	other threads:[~2022-07-26 14:48 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-07-26 12:23 Question about performance comparison between virtio-fs and virtio-blk Hao Xu
2022-07-26 12:55 ` Stefan Hajnoczi
2022-07-26 13:17   ` Vivek Goyal
2022-07-26 14:41     ` Hao Xu [this message]
2022-07-26 15:37       ` Vivek Goyal

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=1d1f7854-209a-a985-e266-633ca14609da@linux.dev \
    --to=hao.xu@linux.dev \
    --cc=qemu-devel@nongnu.org \
    --cc=stefanha@gmail.com \
    --cc=vgoyal@redhat.com \
    --cc=virtio-fs@redhat.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).