public inbox for gentoo-user@lists.gentoo.org
 help / color / mirror / Atom feed
From: Florian Philipp <lists@f_philipp.fastmail.net>
To: gentoo-user@lists.gentoo.org
Subject: Re: [gentoo-user] Normal disk speed?
Date: Thu, 30 Sep 2010 15:10:42 +0200	[thread overview]
Message-ID: <201009301510.43043.lists@f_philipp.fastmail.net> (raw)
In-Reply-To: <AANLkTikO0WGfQjHMuCa_2Z0gdGa5Ovg97iQGU5FRekAK@mail.gmail.com>

Am Donnerstag 30 September 2010, 12:58:36 schrieb Adam Carter:
> Taring my mp3 collection from 2.5in 500MB internal sata drive (sda) to
> esata 3.5in 500MB drive (sdb) and it seems slow. In vmstat i can see that
> the external drive writes faster than the internal can read (external has
> periods of inactivity)
[...]
> So 21221MB in 610 seconds = 35 MB/s
> 
> # hdparm -t /dev/sda
> 
> /dev/sda:
>  Timing buffered disk reads:  220 MB in  3.01 seconds =  73.14 MB/sec (77
> with --direct)
[...] 
> So the should i expect filesystem (reiser3) and other overhead to cut the
> read performance to less than half of what hdparm reports? Anything else i
> can look at to speed it up? Im using CFQ io scheduler.

35 MB/s is a pretty normal value for a 5400 RPM laptop HDD.

An HDD gets slower when you read the inner tracks.  The angular velocity is 
constant (5400 RPM) while the tangential velocity gets lower with the radius.

Inner tracks are mapped to the sectors at the far end of the partition table. 
That's why you should always put swap and system partitions at the front of 
your partition table and use its end for bulk data.

I guess your mp3 collection is stored somewhere at the middle or end of your 
internal disk (inner tracks) while your external disk is nearly empty and 
therefore stores data on the outer tracks. 

Hope this helps.
Florian Philipp



  reply	other threads:[~2010-09-30 13:11 UTC|newest]

Thread overview: 26+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2010-09-30 10:58 [gentoo-user] Normal disk speed? Adam Carter
2010-09-30 13:10 ` Florian Philipp [this message]
2010-09-30 16:00   ` Peter Humphrey
2010-09-30 16:12     ` [gentoo-user] " Nikos Chantziaras
2010-09-30 16:50     ` [gentoo-user] " Florian Philipp
2010-09-30 21:43       ` Peter Humphrey
2010-09-30 13:26 ` [gentoo-user] " James
2010-09-30 16:53 ` [gentoo-user] " Volker Armin Hemmann
2010-10-01  1:12   ` Adam Carter
2010-10-01  4:41     ` Volker Armin Hemmann
2010-10-01  8:42     ` Florian Philipp
2010-10-01 16:23       ` Volker Armin Hemmann
2010-10-02  2:11         ` Adam Carter
2010-10-02 11:54         ` Florian Philipp
2010-10-02 12:11           ` Volker Armin Hemmann
2010-10-02 12:44             ` Florian Philipp
2010-10-02 15:06               ` Florian Philipp
2010-10-01  9:05     ` Daniel Troeder
2010-10-01 14:40       ` [gentoo-user] " James
2010-10-02 17:29         ` Daniel Troeder
2010-10-03  0:13           ` James
2010-10-06  8:04             ` Adam Carter
2010-10-06 18:52               ` Daniel Troeder
2010-10-06 22:59                 ` Adam Carter
2010-10-07  9:33                   ` Daniel Troeder
2010-10-18 10:03                     ` Adam Carter

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=201009301510.43043.lists@f_philipp.fastmail.net \
    --to=lists@f_philipp.fastmail.net \
    --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