RE: instance and disk layout

Bridget Tough question! It depends upon how many RAID groups of disks you contemplate creating and the activity on each database. Split out rootdbs, physlog and logilog dbspaces. maximise the spread of acivity over as many disks as possible. Spread your temp spaces as far as practical - to spread the load. Do you have any OS constraints, such as maximum number of slices per disk? You also need knowledge of the application. I spend some time planning each installation with full information on disks, OS, application, expected data, clients expected usr of that data. MW -----Original Message----- From: owner-informix-list@iiug.iiug.org [mailto:owner-informix-list@iiug.iiug.org]On Behalf Of Bridget Reitsma Sent: Tuesday, May 09, 2000 1:41 PM To: informix-list@iiug.org Subject: instance and disk layout Hi, I am currently building a new production server and would like some recommendations on disk layout. We will be using RAID 1+0. I have two instances - the first has one database in it and the second has two databases in it. I have always kept data and indexes in a separate dbspaces but usually on the same disk - would it be wise or give me better performance if I was to separate them out onto separate disks as well (so separate dbspaces on separate disks)? Also I currently have a small temp space on each disk (250mb) - should I duplicate this for the second instance but in reverse order (ie temp01 is on disk 10 temp02 is on disk 09) or does it make no difference as the engine will choose what temp space to write to (while we are on this subject I don't fully understand how the engine chooses the temp space and whether having all these small temps spaces will make it run in parallel.). Lastly should I have my logs (logical and physical) in separate dbspaces on separate disks? thanks for all your ideas regards Bridget