-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1


On dinsdag, september 3, 2002, at 06:16 , Roger Deschner wrote:

I have had to use the brute force method - "dumb load balancing". That
is, squeezing the database into the shape I want with DELETE DBVOL.
Making this work takes careful advance planning, but the payoff can be
big. RAID may make this harder, since the underlying physical disk
structure may be hidden from you.

Exactly. Well, I did the same here, and got noticable performance
increase by splitting my raid10 into seperate raid1 arrays and defining
dbvols on each of the raid's. It seems taht the fewer 'smart' things
like raid10, lvm striping and mere things like taht are in the path, the
better the database performs.

I cannot speak for RAID, because I have avoided it, but for JBOD disks,
is not a big problem to have DB and Log on the same disk, except that
their I/O patterns are very different, so you might want to tune them
separately. It is also not a problem to have multiple DB extents on the
same physical disk, as long as they are adjacent to one another.

True, in most cases this means having one large volume. This makes them
as adjactent as they can be ;)

As for logvolumes. I noticed that my dbvol disks are so busy that
sepeparting the log really did help in performance of both the log and
the db.

- ---
Met vriendelijke groeten,

Remco Post

SARA - Stichting Academisch Rekencentrum Amsterdam    http://www.sara.nl
High Performance Computing  Tel. +31 20 592 8008    Fax. +31 20 668 3167
PGP keys at http://home.sara.nl/~remco/keys.asc

"I really didn't foresee the Internet. But then, neither did the computer
industry. Not that that tells us very much of course - the computer
industry
didn't even foresee that the century was going to end." -- Douglas Adams


-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.0.7 (Darwin)

iD8DBQE9dcIXBIoCv9yTlOwRAntxAJ940CJyd76MNz27XECb/a+43w9JJQCfXj3h
L0e8u7akAjA2kC5tILQ0/rE=
=8KZJ
-----END PGP SIGNATURE-----