mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Paul Venezia <pvenezia@jpj.net>
To: linux-kernel@vger.kernel.org
Subject: I/O issues, iowait problems, 2.4 v 2.6
Date: 10 Nov 2003 21:53:33 -0500	[thread overview]
Message-ID: <1068519213.22809.81.camel@soul.jpj.net> (raw)

I've been running some benchmarks on 2.4 v 2.6 recently, and came across
another oddity. 

Running smbtorture's NBENCH test against the 2.6 kernel shows a
significant performance disparity vs Redhat 2.4.20 or 2.4.22. The target
system is running RH AS 3.0, and is an IBM x335 dual P4 XEON with 1.5GB
RAM, Broadcom gigabit NIC linked at 1000/full and an MPT RAID
controller.

Running a 12-client NBENCH test against this server running 2.4.22
consistently produces a result of ~33MB/s. Running 2.6.0-test9 through
bk-11 however, produces a much lower result, usually ~14MB/s. The test
will start at ~80MB/s, sustained for 10-15 seconds, then throughput
drops precipitously, and the file transfers slow to a crawl. The target
system shows that it's 100% I/O bound, but I can't seem to locate the
constraint. iostat and sar don't show anything out of the ordinary, but
top shows the CPUs at 99% iowait. Eventually, the bottleneck disappears,
and the performance increases, but never substantially. 

I can reproduce this at will on this system, and a dual Itanium2 system
with Samba 2.2.8a and 3.0. Removing Samba from the equation, copying a
550MB file via NFS takes 240s under 2.6.0-test9-bk11 (~2.5MB/s average),
exhibiting the same iowait problem, while under 2.4.22 the same transfer
takes ~13s (~44MB/s average) without any iowait issues. A raw IP
throughput test shows ~900Mb throughput between the two boxes.

This could be a driver issue, but I don't have any other test boxes at
the moment. I can provide any debug info requested.

-Paul


             reply	other threads:[~2003-11-11  3:04 UTC|newest]

Thread overview: 16+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2003-11-11  2:53 Paul Venezia [this message]
2003-11-11  3:22 ` Linus Torvalds
2003-11-11  3:54 ` Andrew Morton
2003-11-11  4:02   ` Paul Venezia
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=1068519213.22809.81.camel@soul.jpj.net \
    --to=pvenezia@jpj.net \
    --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®