From: Rogier Wolff <R.E.Wolff@BitWizard.nl>
To: Mark Knecht <markknecht@gmail.com>
Cc: "Jeff Moyer" <jmoyer@redhat.com>,
"Rogier Wolff" <R.E.Wolff@bitwizard.nl>,
"Greg Freemyer" <greg.freemyer@gmail.com>,
"Bruno Prémont" <bonbons@linux-vserver.org>,
linux-kernel@vger.kernel.org, linux-ide@vger.kernel.org
Subject: Re: Slow disks.
Date: Mon, 27 Dec 2010 01:34:56 +0100 [thread overview]
Message-ID: <20101227003456.GG18227@bitwizard.nl> (raw)
In-Reply-To: <AANLkTi=qAGCFU0u8joKVR4o4QQaRZt1XWfOPSt8eiD3r@mail.gmail.com>
On Sun, Dec 26, 2010 at 03:38:51PM -0800, Mark Knecht wrote:
> First, the drives are 4K sector so it's really important to get them
> on the right partition boundary. Installing Gentoo requires that we
> un-tar some large-ish files. IIRC on a 512 byte boundary these drives
> took 20-30 minutes to do this. On a 4K boundary they took about 1
> minute. I know that doesn't make sense but those were my numbers, and
> it's a very high end Intel i7-980x MB so there wasn't any other
> problem I could find.
Mark,
Thanks for your contribution. You're seeing a 20-30 fold performance
issue, where only about 2x would be expected. So to test this theory
I'll see if we can evacuate a partition, untar a large-ish file as a
benchmark, and then see if we can improve that by changing the
alignment of the partition. (hmm. Maybe we should do things the other
way around. First find a tar-workload that takes about 1 minute on a
properly working drive, and then we can wait up to 30 minutes for it
to finish on the improper setup.).
Being able to reproduce a problem at will is a great progress to being
able to solve it!
Roger.
--
** R.E.Wolff@BitWizard.nl ** http://www.BitWizard.nl/ ** +31-15-2600998 **
** Delftechpark 26 2628 XH Delft, The Netherlands. KVK: 27239233 **
*-- BitWizard writes Linux device drivers for any device you may have! --*
Q: It doesn't work. A: Look buddy, doesn't work is an ambiguous statement.
Does it sit on the couch all day? Is it unemployed? Please be specific!
Define 'it' and what it isn't doing. --------- Adapted from lxrbot FAQ
next prev parent reply other threads:[~2010-12-27 0:34 UTC|newest]
Thread overview: 29+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <20101220141553.GA6088@bitwizard.nl>
2010-12-20 18:06 ` Slow disks Bruno Prémont
2010-12-20 18:32 ` Greg Freemyer
2010-12-22 10:43 ` Rogier Wolff
2010-12-22 15:59 ` Greg Freemyer
2010-12-22 16:27 ` Jeff Moyer
2010-12-22 22:44 ` Rogier Wolff
2010-12-23 14:40 ` Jeff Moyer
2010-12-23 17:01 ` Rogier Wolff
2010-12-23 17:47 ` Jeff Moyer
2010-12-23 18:51 ` Greg Freemyer
2010-12-23 19:10 ` Jaap Crezee
2010-12-23 22:09 ` Greg Freemyer
2010-12-24 11:40 ` Rogier Wolff
2010-12-26 23:05 ` Greg Freemyer
2010-12-27 0:27 ` Rogier Wolff
2010-12-27 7:21 ` Stan Hoeppner
2010-12-24 10:45 ` Rogier Wolff
2010-12-26 23:38 ` Mark Knecht
2010-12-27 0:34 ` Rogier Wolff [this message]
2010-12-27 3:12 ` Mark Knecht
2010-12-27 18:20 ` Krzysztof Halasa
2010-12-24 13:01 ` Krzysztof Halasa
2010-12-24 15:24 ` Michael Tokarev
2010-12-24 20:58 ` Krzysztof Halasa
2010-12-25 12:14 ` Rogier Wolff
2010-12-25 12:19 ` Mikael Abrahamsson
2010-12-26 21:40 ` Rogier Wolff
2010-12-26 23:17 ` Greg Freemyer
2010-12-26 23:49 ` Rogier Wolff
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=20101227003456.GG18227@bitwizard.nl \
--to=r.e.wolff@bitwizard.nl \
--cc=bonbons@linux-vserver.org \
--cc=greg.freemyer@gmail.com \
--cc=jmoyer@redhat.com \
--cc=linux-ide@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=markknecht@gmail.com \
/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;
as well as URLs for NNTP newsgroup(s).