From: Willie Wong <wwong@Math.Princeton.EDU>
To: gentoo-user@lists.gentoo.org
Subject: Re: [gentoo-user] 1-Terabyte drives - 4K sector sizes? -> bar performance so far
Date: Sun, 14 Feb 2010 20:17:40 -0500 [thread overview]
Message-ID: <20100215011740.GA27687@math.princeton.edu> (raw)
In-Reply-To: <201002150148.05937.Warp_7@gmx.de>
On Mon, Feb 15, 2010 at 01:48:01AM +0100, Frank Steinmetzger wrote:
> Sorry if I reheat a topic that some already consider closed. I used the
> weekend to experiment on that stuff and need to report my results. Because
> they startle me a little.
>
> I first tried different start sectors around sector 63: 63, 64, 66, 68 etc.
> They showed nearly the same results in speed. So I almost thought that my
> drive, albeit being new and of high capacity, is not affected by this yet.
>
> But then I tested my main media partition, which starts in the middle of the
> disk. I downloaded a portage snapshot and put it into a ramdisk, so reading
> it would not manipulate measurements. I also copied a 1GB file into that
> ramdisk to test consecutive writes.
>
> As a start sector I chose 288816640, which is divisible by 64. The startling
> result: this gave the lowest performance. If the partition starts in one of
> the sectors behind it, performance was always better. I repeated the test
> several times to confirm it. How do you explain this? :-?
>
> The following table shows the ‘real’ value from the output of the time
> command. SS means the aforementioned start sector with SS % 64 == 0.
>
> action SS (1st) SS (2nd) SS+2 SS+4 SS+6 SS+8
> -------------+----------+----------+----------+----------+----------+----------
> untar portage 3m12.517 2m55.916 1m46.663 1m35.341 1m47.829 1m43.677
> rm portage 4m11.109 3m54.950 3m18.820 3m11.378 3m21.804 3m12.433
> cp 1GB file 0m21.383 0m13.558 0m14.920 0m12.813 0m13.407 0m13.681
Instead of guessing using this rather imprecise metric, why not just
look up the serial number of your drive and see what the physical
sector size is? If you don't want to open your box, you can usually
get the information from dmesg.
Only caveat: don't trust the harddrive to report accurate geometry.
This whole issue is due to the harddrives lying about their physical
geometry to be compatible with older versions of Windows. So the
physical sector size listed in dmesg may not be the real one. Which is
why you are advised to look up the model number on the vendor's
website yourself to determine the physical sector size.
W
--
Willie W. Wong wwong@math.princeton.edu
Data aequatione quotcunque fluentes quantitae involvente fluxiones invenire
et vice versa ~~~ I. Newton
next prev parent reply other threads:[~2010-02-15 1:18 UTC|newest]
Thread overview: 78+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-02-07 16:27 [gentoo-user] 1-Terabyte drives - 4K sector sizes? -> bar performance so far Mark Knecht
2010-02-07 17:30 ` Alexander
2010-02-07 18:19 ` Volker Armin Hemmann
2010-02-07 19:26 ` Mark Knecht
2010-02-07 18:38 ` Mark Knecht
2010-02-07 19:16 ` Volker Armin Hemmann
2010-02-07 19:39 ` Willie Wong
2010-02-07 20:31 ` Mark Knecht
2010-02-07 21:59 ` Kyle Bader
2010-02-07 21:42 ` Mark Knecht
2010-02-08 2:08 ` Willie Wong
2010-02-08 17:10 ` Mark Knecht
2010-02-08 18:52 ` Valmor de Almeida
2010-02-08 20:34 ` Paul Hartman
2010-02-09 0:27 ` Neil Bothwick
2010-02-09 12:46 ` Stroller
2010-02-09 13:34 ` Neil Bothwick
2010-02-09 23:37 ` Iain Buchanan
2010-02-10 6:31 ` Volker Armin Hemmann
2010-02-10 7:11 ` Iain Buchanan
2010-02-10 8:37 ` Volker Armin Hemmann
2010-02-10 8:43 ` Volker Armin Hemmann
2010-02-09 13:35 ` Volker Armin Hemmann
2010-02-09 13:57 ` J. Roeleveld
2010-02-09 15:11 ` Stroller
2010-02-09 15:27 ` J. Roeleveld
2010-02-09 17:38 ` Stroller
2010-02-09 18:25 ` Mark Knecht
2010-02-09 19:29 ` J. Roeleveld
2010-02-09 15:43 ` Neil Bothwick
2010-02-09 17:17 ` Stroller
2010-02-09 20:30 ` Neil Bothwick
2010-02-09 18:03 ` Neil Walker
2010-02-09 19:37 ` J. Roeleveld
2010-02-09 23:52 ` Iain Buchanan
2010-02-10 1:16 ` Stroller
2010-02-10 6:59 ` Neil Walker
2010-02-10 7:31 ` Iain Buchanan
2010-02-10 1:28 ` Stroller
2010-02-10 11:14 ` J. Roeleveld
2010-02-10 16:37 ` Stroller
2010-02-10 17:26 ` J. Roeleveld
2010-02-10 20:48 ` Stroller
2010-02-10 0:11 ` Peter Humphrey
2010-02-10 6:48 ` Neil Walker
2010-02-09 17:33 ` Paul Hartman
2010-02-09 7:47 ` J. Roeleveld
2010-02-09 23:22 ` Iain Buchanan
2010-02-10 7:08 ` Alan McKinnon
2010-02-10 10:56 ` J. Roeleveld
2010-02-10 10:53 ` J. Roeleveld
2010-02-10 11:03 ` Volker Armin Hemmann
2010-02-10 11:17 ` J. Roeleveld
2010-02-10 11:24 ` Volker Armin Hemmann
2010-02-08 5:25 ` Valmor de Almeida
2010-02-08 19:57 ` Stroller
2010-02-09 0:05 ` Frank Steinmetzger
2010-02-09 0:37 ` Mark Knecht
2010-02-09 2:48 ` Frank Steinmetzger
2010-02-09 17:09 ` Frank Steinmetzger
2010-02-09 18:21 ` Mark Knecht
2010-02-09 21:13 ` Frank Steinmetzger
2010-02-09 22:17 ` J. Roeleveld
2010-02-09 22:54 ` Mark Knecht
2010-02-10 0:31 ` Iain Buchanan
2010-02-10 1:27 ` Mark Knecht
2010-02-10 7:06 ` Iain Buchanan
2010-02-09 16:31 ` Mark Knecht
2010-02-12 9:06 ` Mick
2010-02-12 12:14 ` Mark Knecht
2010-02-09 0:47 ` Stroller
2010-02-09 2:20 ` Willie Wong
2010-02-15 0:48 ` Frank Steinmetzger
2010-02-15 1:17 ` Willie Wong [this message]
2010-02-15 3:17 ` Mark Knecht
2010-02-15 18:03 ` Frank Steinmetzger
2010-02-15 23:53 ` Alex Schuster
2010-02-16 17:35 ` Frank Steinmetzger
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=20100215011740.GA27687@math.princeton.edu \
--to=wwong@math.princeton.edu \
--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