From: Volker Armin Hemmann <volkerarmin@googlemail.com>
To: gentoo-user@lists.gentoo.org
Subject: Re: [gentoo-user] 1-Terabyte drives - 4K sector sizes? -> bar performance so far
Date: Sun, 7 Feb 2010 20:16:34 +0100 [thread overview]
Message-ID: <201002072016.35000.volkerarmin@googlemail.com> (raw)
In-Reply-To: <5bdc1c8b1002071038q7f9d379fm4b3f4fffecfaba17@mail.gmail.com>
On Sonntag 07 Februar 2010, Mark Knecht wrote:
> On Sun, Feb 7, 2010 at 9:30 AM, Alexander <b3nder@yandex.ru> wrote:
> > On Sunday 07 February 2010 19:27:46 Mark Knecht wrote:
> >> Every time there is an apparent delay I just see the hard drive
> >> light turned on solid. That said as far as I know if I wait for things
> >> to complete the data is there but I haven't tested it extensively.
> >>
> >> Is this a bad drive or am I somehow using it incorrectly?
> >
> > Is there any related info in dmesg?
>
> No, nothing in dmesg at all.
>
> Here are two tests this morning. The first is to the 1T drive, the
> second is to a 120GB drive I'm currently using as a system drive until
> I work this out:
>
> gandalf TestMount # time tar xjf /mnt/TestMount/portage-latest.tar.bz2
> -C /mnt/TestMount/usr
>
> real 8m13.077s
> user 0m8.184s
> sys 0m2.561s
> gandalf TestMount #
>
>
> mark@gandalf ~ $ time tar xjf /mnt/TestMount/portage-latest.tar.bz2 -C
> /home/mark/Test_usr/
>
> real 0m39.213s
> user 0m8.243s
> sys 0m2.135s
> mark@gandalf ~ $
>
> 8 minutes vs 39 seconds!
>
> The amount of data written appears to be the same:
>
> gandalf ~ # du -shc /mnt/TestMount/usr/
> 583M /mnt/TestMount/usr/
> 583M total
> gandalf ~ #
>
>
> mark@gandalf ~ $ du -shc /home/mark/Test_usr/
> 583M /home/mark/Test_usr/
> 583M total
> mark@gandalf ~ $
>
>
> I did some reading at the WD site and it seems this drive does use the
> 4K sector size. The way it's done is the addressing on cable is still
> 512 byte 'user sectors', but they are packed into 4K physical sectors
> and internal hardware does the mapping.
>
> I suspect the performance issue is figuring out how to get the file
> system to keep things on 4K boundaries. I assume that's what the 4K
> block size is for when building the file system but I need to go find
> out more about that. I did not select it specifically. Maybe I need
> to.
>
> Thanks,
> Mark
no. 4k block size is the default for linux filesystems. But you might have
'misaligned' the partitions. There is a lot of text to read about
'eraseblocks' on ssds and how important it is to align the partitions. You
might want to read up on that to learn how to align partitions.
next prev parent reply other threads:[~2010-02-07 20:03 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 [this message]
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
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=201002072016.35000.volkerarmin@googlemail.com \
--to=volkerarmin@googlemail.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