All of lore.kernel.org
 help / color / mirror / Atom feed
From: Vincent Fu <vincentfu@gmail.com>
To: Thomas Schneider <74cmonty@gmail.com>, fio@vger.kernel.org
Subject: Re: Using fio with adjusted parameters for use case "Hana DB"
Date: Tue, 7 Mar 2023 10:17:21 -0500	[thread overview]
Message-ID: <119de702-3f3d-a21b-0e0a-2d6544dcc9c7@gmail.com> (raw)
In-Reply-To: <7158878c-c788-a75d-00dc-30900eeb2f1f@gmail.com>

On 3/7/23 09:30, Thomas Schneider wrote:
> Hello,
> 
> I'm starting evaluating usage of fio <https://github.com/axboe/fio>.
> 
> My goal is to benchmark different storage device types, e.g. SSD and 
> shared storage, that is close to the I/O workload generated by the 
> "real" application: Hana DB.
> 
> But before defining this "application related benchmark" I would run a 
> generic benchmark first that gives an idea of the IO performance of the 
> relevant storage device; this generic benchmark is using options that 
> are well known to deliver meaningful results with an acceptable (short) 
> runtime.
> 
> The idea behind this strategy is:
> If the generic benchmark already indicates poor IO performance, there's 
> no need to execute another benchmark that simulates the "real" application.
> 
> Could you please share some information of this generic benchmark(s) for 
> devices SSD, RAID and NFS share (e.g. NetApp, EMC)?
> 
> 
> Regards
> Thomas
> 

Thomas, you could start with this:

https://www.snia.org/tech_activities/standards/curr_standards/pts

Vincent

  reply	other threads:[~2023-03-07 15:20 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-03-07 14:30 Using fio with adjusted parameters for use case "Hana DB" Thomas Schneider
2023-03-07 15:17 ` Vincent Fu [this message]
  -- strict thread matches above, loose matches on Subject: below --
2023-03-01 16:16 Thomas Schneider

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=119de702-3f3d-a21b-0e0a-2d6544dcc9c7@gmail.com \
    --to=vincentfu@gmail.com \
    --cc=74cmonty@gmail.com \
    --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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.