Fwd: disk diagnostics

[Bill Hacker]

r.dragonflybsd.org>	 <8613c4330607260344x54d1a62eseb72404c9164fa52 at xxxxxxxxxxxxxx> <8613c4330607260344q5b883258w67c2cad1789831d5 at xxxxxxxxxxxxxx>
In-Reply-To: <8613c4330607260344q5b883258w67c2cad1789831d5 at xxxxxxxxxxxxxx>
Content-Type: text/plain; charset=us-ascii; format=flowed
Content-Transfer-Encoding: 7bit
Lines: 55
Message-ID: <44c7de28$0$775$415eb37d at xxxxxxxxxxxxxxxxxxxxxxxxxxxxxx>
NNTP-Posting-Host: 69.175.228.110
X-Trace: 1153949225 crater_reader.dragonflybsd.org 775 69.175.228.110
Xref: crater_reader.dragonflybsd.org dragonfly.users:6546

Pieter Dumon wrote:

*snip*

> ... I get the same problem for instance when untarring an
> archive of some tens of MB: it takes ages.
>

I haven't had a DragonFly install active for over a year, but using a tarball we 
all have access to - the 98.5 MB DFLY 1.6 iso, I get:

=======

2U server:

time tar xfz dfly-1.6.0_REL.iso.gz

4.896u 2.366s 0:22.07 32.8%     75+3681k 411+1316io 0pf+0w

DreeBSD 6.1 AMD-64, 3 GHz Pentium-D Dual-Core with 2 GB DDR
Mount was on twin IBM/Hitachi 80 GB PATA UDMA 133 HDD, gmirror software RAID1

Not sure if it matters for an I/O speed test, but the AMD-64 toolset gives me 
*many* error messages of the general form:

Unsupported RRIP extension for 56
  PN(16): 16 00 00 00 00 00 00 16 38 00 00 00 00 00 00 38

=======

1U Server:

time tar xfz dfly-1.6.0_REL.iso.gz

real    0m20.255s
user    0m17.747s
sys     0m2.363s

FreeBSD 4.11-STABLE, 2000+ VIA C3 Samuel 2 (796.10-MHz clock) 1 GB DDR
Mount was on twin IBM 60 GB UDMA 100 HDD, atacontrol software RAID1

=======

Software RAID1 on obsolescent drives such as these is nowhere near 'bleeding 
edge', so DragonFly on your hardware should be comparable, if not better - eg 
complete in *seconds* what you are reporting in *minutes*.

Something just has to be wrong with your set up.

HTH,

Bill