From: Simon <turner25@gmail.com>
To: gentoo-user@lists.gentoo.org
Subject: Re: [gentoo-user] {OT} USB 3.0 hard drive speed test
Date: Thu, 11 Aug 2011 13:57:04 -0400 [thread overview]
Message-ID: <CAN1q39XjceAtg=a9JoM0BqgeVDABZ98k2kL83Ues-PnX0Rwn+g@mail.gmail.com> (raw)
In-Reply-To: <1482551.25fYdY8kaD@localhost>
[-- Attachment #1: Type: text/plain, Size: 2052 bytes --]
It is my opinion that benchmarks should be done with a real benchmark tool.
Try with bonnie++
This will really show you the strengths and weaknesses of your setup.
Good luck,
Simon
On Thu, Aug 11, 2011 at 1:49 PM, Volker Armin Hemmann <
volkerarmin@googlemail.com> wrote:
> Am Donnerstag 11 August 2011, 10:30:04 schrieb Mark Knecht:
> > On Thu, Aug 11, 2011 at 10:12 AM, Grant <emailgrant@gmail.com> wrote:
> > > I'm testing this USB 3.0 bus-powered hard drive:
> > >
> > > http://www.amazon.com/gp/product/B0041OSQ9S
> > >
> > > and I get:
> > >
> > > # hdparm -tT /dev/sdb
> > > /dev/sdb:
> > > Timing cached reads: 8006 MB in 2.00 seconds = 4004.33 MB/sec
> > > Timing buffered disk reads: 252 MB in 3.01 seconds = 83.63 MB/sec
> > >
> > > # hdparm -tT /dev/sdb
> > > /dev/sdb:
> > > Timing cached reads: 8230 MB in 2.00 seconds = 4116.54 MB/sec
> > > Timing buffered disk reads: 252 MB in 3.02 seconds = 83.55 MB/sec
> > >
> > > # hdparm -tT /dev/sdb
> > > /dev/sdb:
> > > Timing cached reads: 8446 MB in 2.00 seconds = 4224.36 MB/sec
> > > Timing buffered disk reads: 230 MB in 3.02 seconds = 76.28 MB/sec
> > >
> > > Wikipedia says USB 3.0 has transmission speeds of up to 5 Gbit/s.
> > > Doesn't MB/sec denote mega*bytes* per second?
> > >
> > > - Grant
> >
> > 4000MB/s = 4Gb/s
>
>
> please read man hdparm
>
> -T Perform timings of cache reads for benchmark and comparison
> purposes.
> For meaningful results, this operation
> should be repeated 2-3 times on an otherwise inactive system
> (no
> other active processes) with at least a couple
> of megabytes of free memory. This displays the speed of
> reading
> directly from the Linux buffer cache without
> disk access. This measurement is essentially an indication of
> the throughput of the processor, cache, and mem-
> ory of the system under test.
>
>
> as you can see, those numbers have nothing to do with the transport.
>
> And 80mb/sec for a harddisk is really, really good.
>
> --
> #163933
>
>
[-- Attachment #2: Type: text/html, Size: 2831 bytes --]
next prev parent reply other threads:[~2011-08-11 17:58 UTC|newest]
Thread overview: 23+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-08-11 17:12 [gentoo-user] {OT} USB 3.0 hard drive speed test Grant
2011-08-11 17:27 ` covici
2011-08-11 17:30 ` Mark Knecht
2011-08-11 18:25 ` Grant
2011-08-18 19:46 ` Grant
2011-08-18 22:46 ` Paul Hartman
2011-08-18 23:32 ` Peter Humphrey
2011-08-20 4:48 ` Paul Hartman
2011-08-12 14:58 ` Michael Mol
2011-08-12 22:03 ` covici
2011-08-11 17:30 ` Mark Knecht
2011-08-11 17:49 ` Volker Armin Hemmann
2011-08-11 17:57 ` Simon [this message]
2011-08-11 18:50 ` Grant
2011-08-11 18:59 ` Alan McKinnon
2011-08-11 20:20 ` Paul Hartman
2011-08-12 2:04 ` Grant
2011-08-12 8:54 ` Peter Humphrey
2011-08-11 18:27 ` Grant
2011-08-11 18:34 ` Mark Knecht
2011-08-11 18:52 ` Grant
2011-08-11 19:04 ` Alan McKinnon
2011-08-11 17:46 ` Volker Armin Hemmann
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='CAN1q39XjceAtg=a9JoM0BqgeVDABZ98k2kL83Ues-PnX0Rwn+g@mail.gmail.com' \
--to=turner25@gmail.com \
--cc=gentoo-user@lists.gentoo.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