public inbox for gentoo-user@lists.gentoo.org
 help / color / mirror / Atom feed
From: Grant <emailgrant@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 11:52:50 -0700	[thread overview]
Message-ID: <CAN0CFw0bENkZsiqwB_ERDm8N32kKjq-XFkELLJ-c8xU8F9o6hA@mail.gmail.com> (raw)
In-Reply-To: <CAK2H+ecJaBDukx6xRZ8vaz8sC_KMkNfEOpJu8b36hz9h3eL+Jg@mail.gmail.com>

>>>> 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
>>
>> OK, I thought "B" designated bytes and "b" designated bits.  So when
>> you see something like MB/s or Mb/s there's no way to know if it's
>> referring to megabits or megabytes?
>>
>> - Grant
>
> Nahh, I made a mistake there. 4000MB/S = 4GB/S  - You are correct, at
> least as far as I'm concerned.
>
> Of course Volker, the man with the answer to everything, just told you
> that 80 mega-bit / second was a 'really, really good hard drive' so I
> guess we all make mistakes. ;-)
>
> I was really trying to point out that you ARE getting 80% of the USB
> 3.0 spec in the first number which is the speed of communications
> across the USB cable talking to the drive interface. Sustained storage

As Volker pointed out, I don't think hdparm -T interacts with the USB
system at all.  I get the same rates whether the USB hard drive is
plugged into a 3.0 port or 2.0 port.

- Grant


> rates of the drive don't have anything to do with that though. That
> depends on the drive in the case.
>
> Cheers,
> Mark



  reply	other threads:[~2011-08-11 18:54 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
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 [this message]
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=CAN0CFw0bENkZsiqwB_ERDm8N32kKjq-XFkELLJ-c8xU8F9o6hA@mail.gmail.com \
    --to=emailgrant@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