From: "Jakob Østergaard" <jakob@unthought.net>
To: Jimmie Mayfield <mayfield+usenet@sackheads.org>
Cc: linux-kernel@vger.kernel.org
Subject: Re: Interesting disk throughput performance problem
Date: Sun, 22 Jul 2001 12:29:58 +0200 [thread overview]
Message-ID: <20010722122958.C24136@unthought.net> (raw)
In-Reply-To: <20010721233313.A15232@sackheads.org>
In-Reply-To: <20010721233313.A15232@sackheads.org>; from mayfield+usenet@sackheads.org on Sat, Jul 21, 2001 at 11:33:13PM -0400
On Sat, Jul 21, 2001 at 11:33:13PM -0400, Jimmie Mayfield wrote:
> Hi. I'm running into some disk throughput issues that I can't explain.
> Hopefully someone reading this can offer an explanation.
>
> One of my machines is running 2.4.5 and has 2 hard drives: a 7200 rpm
> ATA100 Maxtor and a 5400 rpm ATA33 IBM. Each drive is a master on its own
> controller (AMI CMD649 as found on the IWill KT266-R). Both drives contain
> reiserfs 3.6x filesystems.
>
> By all local benchmarks, the 7200 rpm drive is the faster drive. But this
> doesn't seem to be the case for large files originating from remote clients.
> Witness:
....
> So I tried the test locally: with the file stored on the 5400rpm drive,
> scp it to localhost and write it to the 7200rpm drive. Results were a little
> below 10MB/sec (CPU near 100% presumably due to encrypting/decrypting on
> the fly).
>
> Any ideas why the 7200rpm drive performs so poorly for remote clients but
> performs wonderfully well when those same operations are performed locally?
This is a wild guess:
Try cat /proc/interrupts
Would the 7200 rpm drive controller happen to share an IRQ with your NIC ?
If so, something is horribly wrong since that shouldn't give that kind of
performance penalty. But it's my best guess :)
--
................................................................
: jakob@unthought.net : And I see the elder races, :
:.........................: putrid forms of man :
: Jakob Østergaard : See him rise and claim the earth, :
: OZ9ABN : his downfall is at hand. :
:.........................:............{Konkhra}...............:
next prev parent reply other threads:[~2001-07-22 10:30 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2001-07-22 3:33 Interesting disk throughput performance problem Jimmie Mayfield
2001-07-22 9:20 ` Hans Reiser
2001-07-22 14:07 ` toon
2001-07-22 14:41 ` Hans Reiser
2001-07-22 10:29 ` Jakob Østergaard [this message]
2001-07-22 10:44 ` Mike Black
2001-07-24 15:06 ` Jimmie Mayfield
-- strict thread matches above, loose matches on Subject: below --
2001-07-24 17:11 Tim Schmielau
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=20010722122958.C24136@unthought.net \
--to=jakob@unthought.net \
--cc=linux-kernel@vger.kernel.org \
--cc=mayfield+usenet@sackheads.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.