From: bartoszek@dx.net.pl
To: fio@vger.kernel.org
Subject: How to perform an random read test, with normal distribution
Date: Wed, 22 Nov 2023 09:29:51 +0100 [thread overview]
Message-ID: <4c92fe6a414a472aaec12b04eae3ffba@dx.net.pl> (raw)
Hi!
I Want to perform a test scenario
I have a "huge" file in which I want to read out blocks of data randomly
with some distribution. For example 20% od blocks in test file will get
~80% od total IO from the engine.
Placement of blocks within the file is not important
The only requirement is that some blocks are read out more frequently
then others, and the distribution of reads is defined by some parameters
Test should simulate a VM image reads during VM startup (or runtime)
where not all files are used, and some are used more often then others.
Is there a way to test such scenario using fio?
Best regards,
Bartosz Wieczorek
next reply other threads:[~2023-11-22 8:36 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-11-22 8:29 bartoszek [this message]
2023-11-22 20:44 ` How to perform an random read test, with normal distribution Vincent Fu
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=4c92fe6a414a472aaec12b04eae3ffba@dx.net.pl \
--to=bartoszek@dx.net.pl \
--cc=fio@vger.kernel.org \
/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).