Date: Sat, 20 Sep 1997 13:16:34 -0500 From: Tom Jackson <toj@gorilla.net> To: freebsd-hardware@FreeBSD.ORG Subject: Opinions please Was: Micropolis Runs Too HOT! Message-ID: <19970920131634.08085@my.domain> In-Reply-To: <199709132341.NAA23393@pegasus.com>; from Richard Foulk on Sat, Sep 13, 1997 at 01:41:23PM -1000 References: <tom@sdf.com> <199709132341.NAA23393@pegasus.com>
next in thread | previous in thread | raw e-mail | index | archive | help
In my previous post I disCussed the heating situation with this 7200rpm scsi
Micropolis drive. I now have two 4-1/2in cooling fans on the midi case, one
blowing over the Mic located in two 5-1/4 in bays and one sucking out at the
back of the case. Although I have return approval for a Fujitsu M2954S, many
claim it will run just hot as the Micropolis. I have run iozone on all of my
drives trying to decide if I should exchange. Although the Mic seems to write
at a good rate the read specs don't look good at all. Would anyone with good
knowledge of this please comment. I need to decide soon.
iozone single results:
---------------------------------------------------------
In the three runs, done separately, the disk cache sized to 11 megabytes.
sd0 is a Micropolis 4421 2.1gb 5400rpm scsi, sd1 is a Micropolis 4345 4.5gb
7200rpm scsi, and sd2 is a Fujitsu M1606sau 1.08gb 5400rpm scsi.
IOZONE: Performance Test of Sequential File I/O -- V2.01 (10/21/94)
By Bill Norcott
Operating System: FreeBSD 2.x -- using fsync()
Send comments to: b_norcott@xway.com
IOZONE writes a 44 Megabyte sequential file consisting of
5632 records which are each 8192 bytes in length.
It then reads the file. It prints the bytes-per-second
rate at which the computer can read and write files.
Writing the 44 Megabyte file, '/usr/ports/iozone.tmp'...11.265625 seconds
Reading the file...7.914062 seconds on sd0
IOZONE performance measurements:
4095409 bytes/second for writing the file
5829792 bytes/second for reading the file
<---
Writing the 44 Megabyte file, '/usr/iozone.tmp'...6.625000 seconds
Reading the file...6.257812 seconds on sd1
IOZONE performance measurements:
6964127 bytes/second for writing the file
7372759 bytes/second for reading the file
<---
Writing the 44 Megabyte file, '/mnt1/iozone.tmp'...6.335938 seconds
Reading the file...5.953125 seconds on sd2
IOZONE performance measurements:
7281849 bytes/second for writing the file
7750105 bytes/second for reading the file
-----------------------------------------------------------
iozone concurrent results:
Concurrent run to all three drives. Disk cache sized itself to 11mb.
IOZONE: Performance Test of Sequential File I/O -- V2.01 (10/21/94)
By Bill Norcott
Operating System: FreeBSD 2.x -- using fsync()
Send comments to: b_norcott@xway.com
IOZONE writes a 44 Megabyte sequential file consisting of
5632 records which are each 8192 bytes in length.
It then reads the file. It prints the bytes-per-second
rate at which the computer can read and write files.
Writing the 44 Megabyte file, '/usr/ports/iozone.tmp'...11.250000 seconds
Reading the file...7.453125 seconds on sd0 (MC4421)
IOZONE performance measurements:
4101097 bytes/second for writing the file
6190335 bytes/second for reading the file
<---
Writing the 44 Megabyte file, '/usr/iozone.tmp'...6.585938 seconds
Reading the file...6.304688 seconds on sd1 (MC4345NS)
IOZONE performance measurements:
7005433 bytes/second for writing the file
7317943 bytes/second for reading the file
<---
Writing the 44 Megabyte file, '/mnt1/iozone.tmp'...6.359375 seconds
Reading the file...5.867188 seconds on sd2 (Fuj M1606S)
IOZONE performance measurements:
7255012 bytes/second for writing the file
7863621 bytes/second for reading the file
I can't tell if this bad performance or the disk might be damaged
Tom
---
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?19970920131634.08085>