Re: Fundamental database design question

Here is what we've done for our production (PeopleSoft) database.

we have 60 disks running on two dual fiberchannel controllers (4 controllers max)

these 60 disks are hardware mirrored so the system only sees 30 devices

Of these 30 devices we've done some striping and I have 14 logical volumes with 2 spares.

Database block size is 8K, OS disk block size is 8K. Stripe size on all disks (note exception below) is 16K

I've put oracle home on one disk (not stiped).
I've got data, hopefully load balanced, on 7
I've put my indexes on 2
I've put my temp space on 2 of these with a large stripe size (64K)
I've got my rollbacks and redologs on 2

I still experience disk I/O bottlenecks occasionally. Some of this is poor SQL tuning, we're working on that. Some of this is poor archetecture, we're working on that. What I've recently done is take some tablespaces where multiple tables exist that get simultaniously read and written and broken them up into multiple tablespaces, migrated the tables, and spread them over multiple disks. It helps.

I guess what I'm trying to say is theory is great but in practice you need to monitor your database load, and make changes based on what is happening.

Dave Received on Mon Aug 14 2000 - 10:00:16 CDT