* Using fio with adjusted parameters for use case "Hana DB"
@ 2023-03-01 16:16 Thomas Schneider
0 siblings, 0 replies; 3+ messages in thread
From: Thomas Schneider @ 2023-03-01 16:16 UTC (permalink / raw)
To: fio
Hello Vincent,
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
^ permalink raw reply [flat|nested] 3+ messages in thread
* Re: Using fio with adjusted parameters for use case "Hana DB"
2023-03-07 14:30 Thomas Schneider
@ 2023-03-07 15:17 ` Vincent Fu
0 siblings, 0 replies; 3+ messages in thread
From: Vincent Fu @ 2023-03-07 15:17 UTC (permalink / raw)
To: Thomas Schneider, fio
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
^ permalink raw reply [flat|nested] 3+ messages in thread
* Using fio with adjusted parameters for use case "Hana DB"
@ 2023-03-07 14:30 Thomas Schneider
2023-03-07 15:17 ` Vincent Fu
0 siblings, 1 reply; 3+ messages in thread
From: Thomas Schneider @ 2023-03-07 14:30 UTC (permalink / raw)
To: fio
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
^ permalink raw reply [flat|nested] 3+ messages in thread
end of thread, other threads:[~2023-03-07 15:20 UTC | newest]
Thread overview: 3+ messages (download: mbox.gz / follow: Atom feed)
-- links below jump to the message on this page --
2023-03-01 16:16 Using fio with adjusted parameters for use case "Hana DB" Thomas Schneider
2023-03-07 14:30 Thomas Schneider
2023-03-07 15:17 ` Vincent Fu
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).