From: "Jakob Østergaard" <jakob@unthought.net>
To: Roy Sigurd Karlsbakk <roy@karlsbakk.net>
Cc: Jens Axboe <axboe@suse.de>, Linux Kernel <linux-kernel@vger.kernel.org>
Subject: Re: Linux i/o tweaking
Date: Thu, 15 Nov 2001 17:41:50 +0100 [thread overview]
Message-ID: <20011115174150.B23020@unthought.net> (raw)
In-Reply-To: <20011115172246.Z27010@suse.de> <Pine.LNX.4.30.0111151731280.13922-100000@mustard.heime.net>
In-Reply-To: <Pine.LNX.4.30.0111151731280.13922-100000@mustard.heime.net>; from roy@karlsbakk.net on Thu, Nov 15, 2001 at 05:32:29PM +0100
On Thu, Nov 15, 2001 at 05:32:29PM +0100, Roy Sigurd Karlsbakk wrote:
> > Could you please try and profile where the time is spent? Boot with
> > profile=2, and then do
> >
> > # readprofile -r
> > # do I/O testing
> > # readprofile | sort -nr
>
> I will.
>
> However ... Is it normal for a server to max out 2xPIII 1266MHz CPUs by
> reading from software RAID-5???
Certainly not.
Well, if you down-scale the experiment it's not. Reading 10.7 MB/sec
will not consume 10% of your two processors.
But queue systems are evil ;) I look forward to seeing the profile.
--
................................................................
: 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-11-15 16:42 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2001-11-15 16:13 Linux i/o tweaking Roy Sigurd Karlsbakk
2001-11-15 16:22 ` Jens Axboe
2001-11-15 16:32 ` Roy Sigurd Karlsbakk
2001-11-15 16:41 ` Jakob Østergaard [this message]
2001-11-15 16:50 ` Roy Sigurd Karlsbakk
2001-11-15 18:17 ` Joel Jaeggli
2001-11-15 18:33 ` Roy Sigurd Karlsbakk
2001-11-15 22:32 ` Lionel Bouton
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=20011115174150.B23020@unthought.net \
--to=jakob@unthought.net \
--cc=axboe@suse.de \
--cc=linux-kernel@vger.kernel.org \
--cc=roy@karlsbakk.net \
/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