From: Tomas Szepe <szepe@pinerecords.com>
To: linux-kernel@vger.kernel.org
Subject: Re: Linux 2.4/2.5 SCSI considerably slower than FreeBSD
Date: Mon, 20 May 2002 01:53:14 +0200 [thread overview]
Message-ID: <20020519235314.GC26417@louise.pinerecords.com> (raw)
In-Reply-To: <3CE5D4FC.DB2CC47E@torque.net> <20020519205015.GC3008@merlin.emma.line.org>
> > $ time sg_dd if=/dev/sg1 of=/dev/null bs=512 count=2m time=1
> > time to transfer data was 18.786448 secs, 57.16 MB/sec
> > 2097152+0 records in
> > 2097152+0 records out
> > real 0m18.799s user 0m0.030s sys 0m3.010s
>
> In a live system (actually, it's idle, but every 5 s, there is a short
> burst of disk activity -- reiserfs and ext3fs in use here, something is
> going on there), sg_dd is not really better than plain dd:
>
> > time sg_dd if=/dev/sg0 of=/dev/null count=1310720
> > Assume default 'bs' (block size) of 512 bytes
> > 1310720+0 records in
> > 1310720+0 records out
> >
> > real 0m24.348s
>
> gives: 27,56 MB/s. A little better than dd, but still much less than FreeBSD's.
hmmm.
# sync; sync; time dd if=/dev/sda of=/dev/null bs=64k count=10000
10000+0 records in
10000+0 records out
real 0m12.809s
user 0m0.020s
sys 0m2.560s
(first read, the data shouldn't have been cached)
-> 48.79 MB/s
I wouldn't suspect there's a problem, the numbers look reasonable.
$ uname -r
2.4.19-pre2
Disk:
Host: scsi0 Channel: 00 Id: 02 Lun: 00
Vendor: SEAGATE Model: ST336706LW Rev: 0109
Type: Direct-Access ANSI SCSI revision: 03
(i.e., 36GiB 160MB/s Seagate Cheetah)
Controller - HP netserver onboard sym53c896.
T.
next prev parent reply other threads:[~2002-05-19 23:53 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-05-18 4:13 Linux 2.4/2.5 SCSI considerably slower than FreeBSD Douglas Gilbert
2002-05-19 20:50 ` Matthias Andree
2002-05-19 23:53 ` Tomas Szepe [this message]
2002-05-23 3:41 ` Douglas Gilbert
-- strict thread matches above, loose matches on Subject: below --
2002-05-17 11:53 Matthias Andree
2002-05-19 12:38 ` Geert Uytterhoeven
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=20020519235314.GC26417@louise.pinerecords.com \
--to=szepe@pinerecords.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