From: John Gluck <jgluckca@home.com>
To: "linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>
Subject: Re: SCSI read performance issues (2.2.19 and 2.4.10)
Date: Wed, 24 Oct 2001 19:23:36 -0400 [thread overview]
Message-ID: <3BD74D77.3B73A446@home.com> (raw)
[-- Attachment #1: Type: text/plain, Size: 1 bytes --]
[-- Attachment #2: Type: message/rfc822, Size: 2440 bytes --]
From: John Gluck <jgluckca@home.com>
To: Andrew Morton <akpm@zip.com.au>
Subject: Re: gdth / SCSI read performance issues (2.2.19 and 2.4.10)
Date: Wed, 24 Oct 2001 18:20:57 -0400
Message-ID: <3BD73EC9.C42CFF6E@home.com>
Hi
Just my experience with 2.4.13
SCSI disk performance. I tested with hdparm peaks at 17 meg /sec. My SCSI
controller and HD are capable of up to 40 meg /sec.
IDE disks on an ATA 33 contoller peak at 20 to 23 megs depending on which disk.
If there's any test you'd like me to try I'll be more than happy to.
John
>
[snip]
> Really? Are you saying that on a controller which can
> do 85 megs/second, you can't read files through the filesystem
> at greater than 17? Which filesystem?
>
> > The result (last 4 lines):
> > c01388fc try_to_free_buffers 55 0.1511
> > c0128b10 file_read_actor 1179 14.0357
> > c01053b0 default_idle 6784 130.4615
> > 00000000 total 8695 0.0065
>
> OK, that's normal and proper. Almost all the kernel time
> is spent copying data.
>
> > Does this suggest that the kernel isn't the bottleneck?
>
> Well... We seem to have three issues here:
>
> 1: Why isn't the controller achieving the manufacturer's
> claimed throughput?
>
> Don't know. Maybe it's the software copy. Maybe it's the
> device driver. Maybe they lied :). It'd be interesting
> to test it on the same machine with the vendor's drivers
> and win2k.
>
> 2: 0-order allocation failures.
>
> 3: Poor `cp' throughput. This one is strange. Perhaps
> `cp' is using a small transfer-size and the kernel's
> readhead isn't working properly. Could you experiment
> with this some more? For example, what happens with
>
> dd if=large_file of=/dev/null bs=4096k
>
> -
> -
> To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
> the body of a message to majordomo@vger.kernel.org
> More majordomo info at http://vger.kernel.org/majordomo-info.html
> Please read the FAQ at http://www.tux.org/lkml/
reply other threads:[~2001-10-24 23:27 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
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=3BD74D77.3B73A446@home.com \
--to=jgluckca@home.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox