mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Paul Venezia <pvenezia@jpj.net>
To: Andrew Morton <akpm@osdl.org>
Cc: linux-kernel@vger.kernel.org
Subject: Re: I/O issues, iowait problems, 2.4 v 2.6
Date: 10 Nov 2003 23:02:08 -0500	[thread overview]
Message-ID: <1068523328.25805.97.camel@soul.jpj.net> (raw)
In-Reply-To: <20031110195433.4331b75e.akpm@osdl.org>

On Mon, 2003-11-10 at 22:54, Andrew Morton wrote:
>  Eventually, the bottleneck disappears,
> > and the performance increases, but never substantially. 
> 
> It's not clear here what direction the data is being transferred in.  Is it
> mostly client->server, or mostly server->client?

Seems to be bidirectional.

> What filesystem is the server using?

ext3

> In which direction was the file transferred?  client to server or server to
> client?  What kernel was running on each?

The client is running AS2.1, RH's 2.4.9-e12. Server is RH AS 3.0, 2.4.22
stock, and 2.6.0-test9, 2.6.0-test9-bk11. Transfers in both directions.
> 
> As next steps I'd suggest that you log into the server and do
> 
> 	time (dd if=/dev/zero of=x bs=1M count=2048 ; sync)
> 
> and
> 
> 	time (dd if=x of=/dev/null bs=1M count=2048 ; sync)
> 
> (this assumes that the machine has less that 2G of memory, to avoid caching
> effects).

The raw file read/write is the ticket. The box tightens right up at 100% iowait.

I'd done bonnie++ i/o tests already, and except for an apparent NPTL issue on the per char,
the block i/o numbers were fine; no abnormal results whatsoever. In fact, block r/w
numbers were improved compared to 2.4.22. Now that I'm looking for it, however, I 
do note extremely elevated iowait numbers during a bonnie++ run. Something in the MPT
modules?

-Paul


  reply	other threads:[~2003-11-11  4:12 UTC|newest]

Thread overview: 16+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2003-11-11  2:53 Paul Venezia
2003-11-11  3:22 ` Linus Torvalds
2003-11-11  3:54 ` Andrew Morton
2003-11-11  4:02   ` Paul Venezia [this message]
2003-11-11  4:28     ` Andrew Morton
2003-11-11  4:22       ` Paul Venezia
2003-11-11  4:24       ` Paul Venezia
2003-11-11  4:54         ` Andrew Morton
2003-11-11  4:55           ` Paul Venezia
2003-11-11  5:44             ` Linus Torvalds
2003-11-11  5:13           ` Paul Venezia
2003-11-11  5:29           ` Paul Venezia
2003-11-11  5:50             ` Andrew Morton
2003-11-11  6:04               ` Paul Venezia
2003-11-11  5:36           ` Linus Torvalds
2003-11-11  4:12   ` Paul Venezia

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=1068523328.25805.97.camel@soul.jpj.net \
    --to=pvenezia@jpj.net \
    --cc=akpm@osdl.org \
    --cc=linux-kernel@vger.kernel.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

all inboxes | Powered by JetHome®