From: Bill Davidsen <davidsen@tmr.com>
To: Linux Portal <linportal@gmail.com>,
Linux Kernel mailing List <linux-kernel@vger.kernel.org>
Subject: Re: Simple utility to measure disk random access time
Date: Tue, 16 Jan 2007 14:01:20 -0500 [thread overview]
Message-ID: <45AD2100.9030900@tmr.com> (raw)
In-Reply-To: <ceccffee0701160649w5e401cf9i433f61beeb26e2b1@mail.gmail.com>
Linux Portal wrote:
> And a few graphs here: http://linux.inet.hr/how_fast_is_your_disk.html
>
> Comments welcome!
These results:
gaimboi:davidsen> ./da /dev/hdb
Seeker v2.0, 2007-01-15, http://linux.inet.hr/how_fast_is_your_disk.html
Benchmarking /dev/hdb [0MB], wait 30 seconds..............................
Results: 565841 seeks/second, 0.00 ms random access time
gaimboi:davidsen> ./da /dev/hda
Seeker v2.0, 2007-01-15, http://linux.inet.hr/how_fast_is_your_disk.html
Benchmarking /dev/hda [19092MB], wait 30
seconds..............................
Results: 49 seeks/second, 20.20 ms random access time
gaimboi:davidsen> ./da /dev/hdc
Seeker v2.0, 2007-01-15, http://linux.inet.hr/how_fast_is_your_disk.html
Benchmarking /dev/hdc [57241MB], wait 30
seconds..............................
Results: 64 seeks/second, 15.56 ms random access time
led to this patch:
RCS file: RCS/disk_access.c,v
retrieving revision 1.1
diff -r1.1 disk_access.c
67a68,72
> if (numblocks <= 0) {
> /* pretty small disk found here */
> printf("Disk too small, size: %d blocks\n", numblocks);
> exit(EXIT_FAILURE);
> }
69a75
>
and this warning:
gaimboi:davidsen> ./da /dev/hdb
Seeker v2.0, 2007-01-15, http://linux.inet.hr/how_fast_is_your_disk.html
Disk too small, size: 0 blocks
--
bill davidsen <davidsen@tmr.com>
CTO TMR Associates, Inc
Doing interesting things with small computers since 1979
prev parent reply other threads:[~2007-01-16 18:59 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-01-16 14:49 Simple utility to measure disk random access time Linux Portal
2007-01-16 19:01 ` Bill Davidsen [this message]
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=45AD2100.9030900@tmr.com \
--to=davidsen@tmr.com \
--cc=linportal@gmail.com \
--cc=linux-kernel@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.