From: "Ryan Shrout" <linux-kernel@amdmb.com>
To: <linux-kernel@vger.kernel.org>
Subject: Re: Slow SCSI Disk Access on AMI Elite 1600 controller
Date: Tue, 14 Aug 2001 18:54:56 -0400 [thread overview]
Message-ID: <06db01c12514$23afc520$b214860a@amdmb> (raw)
In-Reply-To: <Pine.LNX.4.10.10108142225230.12794-100000@coffee.psychology.mcmaster.ca>
> > Timing buffered disk reads: 64 MB in 13.92 seconds = 4.60 MB/sec
> ...
> > 4 - 15K RPM Cheetah SCSI HDDs
>
> each disks will sustain 30-50 MB/s, so yeah, that's kind of low.
>
I changed the drives settings from Write-Through to Write-Back and it went
to 22.5 MB/sec
> > AMI Elite 1600 SCSI RAID controller with 64 MB SDRAM
>
> I wish people would start with relatively simple controllers,
> and only move to fancy ones if they know they need them,
> and can prove that the fancy controller works better.
>
> so for instance, these disks on any PCI ultra2 controller
> will easily sustain 100 MB/s. SW raid5 might slow things down
> if you had, say, a single celeron (260 MB's dram bandwidth),
> but certainly wouldn't effect a dual athlon with ddr.
>
I am using them in a RAID 0+1 configuration, so this kind of card was
needed. Besides, it was a gift (Free!) and I couldn't pass that up.
> > Red Hat Linux 7.2
>
> do you mean with RH's kernel!?!
>
No, actually, its 2.4.6-2smp custom compiled.
> > So, I then started trying to figure out to raise the buffered disk read
> > speed.
>
> do you have a simple, non-raid ultra2 controller around?
>
> > My only solution I came across -- find out if the SCSI
> > controllers/drives were in asynchronous mode and if they are, change
them to
> > synchronous mode.
>
> unless something dramatic is happening, the disks will stay in the
> same mode as they're detected at driver-init time, which should be
> right before your eyes in /var/log/dmesg. well, at least for a non-fancy
> controller. for a gold-plated controller like you have, you need
> to find some way to query the controller, perhaps a serial port,
> or some too provided by AMI. basically that's a non-linux question,
> since the controller has its own little OS that you need to interact with.
>
> > Now, how can I tell what mode my SCSI disks are in and how can I change
it
> > to synchronous if it isn't set that way already?
>
> unless your scsi cabling is utterly botched, they'll be synchronous.
>
Okay, that helps me so I stop looking for that setting! :)
Hopefully, going from 4.5 -> 22.5 MB/sec will be enough to temporarily stop
my mysqld crashing.
Thanks!
Ryan Shrout
next parent reply other threads:[~2001-08-14 22:54 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <Pine.LNX.4.10.10108142225230.12794-100000@coffee.psychology.mcmaster.ca>
2001-08-14 22:54 ` Ryan Shrout [this message]
2001-08-14 20:33 Slow SCSI Disk Access on AMI Elite 1600 controller Ryan Shrout
-- strict thread matches above, loose matches on Subject: below --
2001-08-14 20:32 Ryan Shrout
2001-08-14 20:27 Ryan Shrout
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='06db01c12514$23afc520$b214860a@amdmb' \
--to=linux-kernel@amdmb.com \
--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 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.