LIST OF IO BENCHMARKS

[Joel Sherrill]

On Sat, May 19, 2018, 5:06 PM Udit agarwal <dev.madaari at gmail.com> wrote:

> Hi,
>
> On Fri, May 18, 2018 at 11:19 PM, Gedare Bloom <gedare at rtems.org> wrote:
>
>> Udit,
>>
>> Can you please compare pros/cons of FIO, IOZONE, and Bonnie++,
>> probably in a blog post is a good idea.
>>
> Done, here
> <http://81.4.107.225/wordpress/index.php/2018/05/19/comparing-io-benchmarks-fio-iozone-and-bonnie/>
> is the comparison.
>

That url has a hard-coded IP address in it. GSoC blogs should be hosted
somewhere where they will have a long life with stable URLs.

It looks nice though. :)


>> The GPLv2 is not a problem for test suites / benchmarks. It is only a
>> problem for code that should get merged into the rtems.git.
>>
>> Gedare
>>
>> On Thu, May 17, 2018 at 5:20 AM, Udit agarwal <dev.madaari at gmail.com>
>> wrote:
>> > Hi all,
>> > As discussed in yesterday's IRC meeting, here is the list of different
>> IO
>> > benchmarks(which are supported by FreeBSD) in the decreasing order of
>> their
>> > popularity  :
>> >
>> > FIO - License type:  GPLv2 - Widely accepted for storage device
>> benchmarking
>> > IOZONE - License: Customized - Large number of features, Also used for
>> > storage benchmarking
>> > Bonnie++ - GPLv2 - Widely known filesystem benchmark, Not much used for
>> > storage benchmarking.
>> > IOMETER -  GPLv2 - Out of active development.
>> > IORATE - Flexible - Out of active development
>> >
>> > I have performed SDIO-SDHCI performance analysis using IOZONE. Here are
>> the
>> > results. And i have documented the process on my blog.
>> >
>> > Regards,
>> >
>> > Udit Agarwal
>> >
>> >
>> > _______________________________________________
>> > devel mailing list
>> > devel at rtems.org
>> > http://lists.rtems.org/mailman/listinfo/devel
>>
>
> _______________________________________________
> devel mailing list
> devel at rtems.org
> http://lists.rtems.org/mailman/listinfo/devel
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.rtems.org/pipermail/devel/attachments/20180520/6017c591/attachment-0002.html>