From: Stefan Hajnoczi <stefanha@gmail.com>
To: Hao Xu <hao.xu@linux.dev>
Cc: qemu-devel <qemu-devel@nongnu.org>,
virtio-fs@redhat.com, Vivek Goyal <vgoyal@redhat.com>
Subject: Re: [Virtio-fs] Question about performance comparison between virtio-fs and virtio-blk
Date: Tue, 26 Jul 2022 08:55:38 -0400 [thread overview]
Message-ID: <CAJSP0QUzd7GXK0XN7YBBfEqO6abQSZMdJzW8pEHnz-ZnGetUWA@mail.gmail.com> (raw)
In-Reply-To: <4f2c71a4-609e-6880-04d0-2eb127c55023@linux.dev>
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.
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.
Stefan
next parent reply other threads:[~2022-07-26 12:55 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <4f2c71a4-609e-6880-04d0-2eb127c55023@linux.dev>
2022-07-26 12:55 ` Stefan Hajnoczi [this message]
2022-07-26 13:17 ` [Virtio-fs] Question about performance comparison between virtio-fs and virtio-blk Vivek Goyal
2022-07-26 14:41 ` Hao Xu
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=CAJSP0QUzd7GXK0XN7YBBfEqO6abQSZMdJzW8pEHnz-ZnGetUWA@mail.gmail.com \
--to=stefanha@gmail.com \
--cc=hao.xu@linux.dev \
--cc=qemu-devel@nongnu.org \
--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 read-only IMAP folder(s) and NNTP newsgroup(s).