--l2tH8b0PpxAnh3ot
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
Content-Transfer-Encoding: quoted-printable

Hi,

I'm trying to understand the results of a run of bonnie++.  There is
machine A, which happens to be my desktop station, running a Xen2 dom0
kernel, with ~750MB of RAM and a wd(4) drive attached to a piixide(4)
controller under UDMA5.  So far so good.

There is machine B, which is a newish Dell running i386 with 4GB of
memory (well, 3GB under NetBSD/i386).  I started doing tests on a disk
attached to a mpi(4) device, but I switched to doing tests on a wd(4)
drived attached to a piixide(4) controller under UDMA6.

Note that softdeps are turned on for the considered mount points, and
that both machines run -current from this week.

IO throughput is normal in both cases.  Both seems pretty fast.  Of
course they really haven't the same amount of memory so I used different
file sizes.

Version  1.03       ------Sequential Output------ --Sequential Input- --Ran=
dom-
                    -Per Chr- --Block-- -Rewrite- -Per Chr- --Block-- --See=
ks--
Machine        Size K/sec %CP K/sec %CP K/sec %CP K/sec %CP K/sec %CP  /sec=
 %CP
A                1G 41420  50 39275  26 +++++ +++ 41311  43 42128  13 369.2=
   1

Machine        Size K/sec %CP K/sec %CP K/sec %CP K/sec %CP K/sec %CP  /sec=
 %CP
B                8G 61225  62 61574  40 30519  17 64889  87 65111  21 161.6=
   3

Directory operations are another story:

                    ------Sequential Create------ --------Random Create----=
----
                    -Create-- --Read--- -Delete-- -Create-- --Read--- -Dele=
te--
Machine       files  /sec %CP  /sec %CP  /sec %CP  /sec %CP  /sec %CP  /sec=
 %CP
A               100 10195  26 92042  96 28823  54 14703  39 79685  96 29397=
  53

Machine       files  /sec %CP  /sec %CP  /sec %CP  /sec %CP  /sec %CP  /sec=
 %CP
B               100   590  74 +++++ +++  2145  55   596  74  1013  99  1088=
  69

Only the sequential stats match the performance of machine A.  It shows
up as +++++ here but I got a number a couple of times and it was the
same order as machine A.

But how do I explain the rest?  I mean, "random read".  That's almost 80
times slower!

Partitions info:
A -> g: 122880240  24289776     4.2BSD   2048 16384   328
B -> e:  31461696  33559800     4.2BSD   2048 16384 28104

What's the exact meaning of the last field?  Is it relevant to the
issue?  I simply newfs'd the partition.  The partition on machine A was
newfs'd a long, long time ago.

--=20
Quentin Garnier - cube@cubidou.net - cube@NetBSD.org
"When I find the controls, I'll go where I like, I'll know where I want
to be, but maybe for now I'll stay right here on a silent sea."
KT Tunstall, Silent Sea, Eye to the Telescope, 2004.

--l2tH8b0PpxAnh3ot
Content-Type: application/pgp-signature
Content-Disposition: inline

-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.3 (NetBSD)

iQEVAwUBRO24l9goQloHrPnoAQLA0Af9ExMLh61IZ1VdjZ/c2rYyFNfcbxitnFVe
rajTmaEe1Iil6MZpYh2JO2N4sNo/bxRCeGiJcpKZKzwyFjiabOhbMZr9mLbSDkj1
itieSy3h7Te5b0iQ2uHy1py/EfLn/YzI7eaK9hloBR1fGyntj+NlkaE/dXPms24q
yVkb5ulm20Yq1s5RcGLnlvWxQcYue2iHIwWvx12U/rS0+hEp0fQr6dVwRldPMC5b
RJ8s+VCtUbZqWOtAyYeTJSRFHGUozuQxuJT+8R8ZF6IGKJorC1kvRzlFJ5Kiv96O
a41sG2HDVcAJZP/cePgQP7lqcH2wi1lsoL0O7zqgAepw++RUqJ4S1g==
=eeDu
-----END PGP SIGNATURE-----

--l2tH8b0PpxAnh3ot--