mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Gérard Roudier <groudier@club-internet.fr>
To: paradox3 <paradox3@maine.rr.com>
Cc: linux-kernel@vger.kernel.org, linux-smp@vger.kernel.org
Subject: Re: Poor SCSI drive performance on SMP machine, 2.2.16
Date: Sun, 28 Jan 2001 12:12:17 +0100 (CET)	[thread overview]
Message-ID: <Pine.LNX.4.10.10101281157220.1110-100000@linux.local> (raw)
In-Reply-To: <003f01c088fb$a35c06e0$b001a8c0@caesar>



On Sun, 28 Jan 2001, paradox3 wrote:

> I have an SMP machine (dual PII 400s) running 2.2.16 with one 10,000 RPM IBM
> 10 GB SCSI drive
> (AIC 7890 on motherboard, using aic7xxx.o), and four various IDE drives. The
> SCSI drive
> performs the worst. In tests of writing 100 MB and sync'ing, one of my IDE
> drives takes 31 seconds. The SCSI drive (while doing nothing else) took
> 2 minutes, 10 seconds. This is extremely noticable in file transfers that
> completely
> monopolize the SCSI drive, and are much slower than when involving the IDE
> drives.
> After a large data operation on the SCSI drive, the system will hang for
> several minutes.
> Anyone know what could be causing this? Thanks.
> 
> Attached are some data to help.

You didn't provide enough information for anybody to have a single idea
about the cause of the problem you report, in my opinion.

Just any not too old 10,000 RPM disk is able to sustain more that 25 MB/s
sequential data transfer, but cannot do better than 5 milli-seconds
latency with random IO patterns. So, result for 100 MB transfer can be
less than 4 seconds in the best case but greater than (25000*5)/1000=125
seconds for random 4K IO pattern, for example.

What you want to do, in my opinion, could be:

- Check in the syslog the actual transfer speed that has been negotiated
  for your SCSI disk.
- Also check if error messages related to disk IOs have been reported by 
  the kernel.
- Run some benchmark to check, at least, sequential IO performance (iozone
  for example will fit)

Gérard.

-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@vger.kernel.org
Please read the FAQ at http://www.tux.org/lkml/

  parent reply	other threads:[~2001-01-28 12:13 UTC|newest]

Thread overview: 12+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2001-01-28  7:26 paradox3
2001-01-28  7:48 ` Andre Hedrick
2001-01-28  8:40 ` Bruce Harada
2001-01-28 17:44   ` paradox3
2001-01-28 23:50     ` Johan Kullstam
2001-01-28 19:31   ` Bruce Harada
2001-01-28 19:52     ` paradox3
2001-01-28 19:56     ` paradox3
2001-01-28 11:12 ` Gérard Roudier [this message]
2001-01-28 22:57 paradox3
     [not found] <F65Jqj0CYixMwInhdAH00002ef1@hotmail.com>
2001-01-29  5:02 ` paradox3
2001-01-29 12:58   ` Johan Kullstam

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=Pine.LNX.4.10.10101281157220.1110-100000@linux.local \
    --to=groudier@club-internet.fr \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-smp@vger.kernel.org \
    --cc=paradox3@maine.rr.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

all inboxes | Powered by JetHome®