Dbspace configuration strategy
More questions on my home system. The scenario: Pentium 90 32mb RAM (eventually upgrading to 64) 1.6Gb IDE hd 4Gb SCSI hd 2-1Gb SCSI hd's SCSI CD-ROM SCSI Tandberg tape drive 2 SCSI controllers SCO Openserver 5.05 Online 7.3 UC? (unsure of the release ) My plan is to install the OS on the IDE drive, and split up the SCSI devices across the two controllers. All the SCSI drives will be raw device. I'm wondering what the best approach is to setting up the root, temp and logs dbspaces relative to the data. I'm initially planning on the rootdbs being on one of the 1GB drives, the logs on the other, the data spread across all three drives. No striping planned, though I may mirror at least the rootdbs. OLTP database(s), capacity unknown just yet; probably ~ 100Mb to start. Am I missing anything obvious? Any generally accepted rules of thumb appreciated. Thanks, -mka Michael Ackerbauer SP System Test
In article <76qr6i$nug$1@news.xmission.com>, ackerbau@us.ibm.com wrote: > > More questions on my home system. > > The scenario: > > Pentium 90 > 32mb RAM (eventually upgrading to 64) > 1.6Gb IDE hd > 4Gb SCSI hd > 2-1Gb SCSI hd's > SCSI CD-ROM > SCSI Tandberg tape drive > 2 SCSI controllers > > SCO Openserver 5.05 > Online 7.3 UC? (unsure of the release) > > My plan is to install the OS on the IDE drive, and split up the SCSI > devices across the two controllers. All the SCSI drives will be raw > device. > > I'm wondering what the best approach is to setting up the root, temp and > logs dbspaces relative to the data. I'm initially planning on the rootdbs > being on one of the 1GB drives, the logs on the other, the data spread > across all three drives. No striping planned, though I may mirror at > least the rootdbs. OLTP database(s), capacity unknown just yet; probably > ~ 100Mb to start. > > Am I missing anything obvious? Any generally accepted rules of thumb > appreciated. > > Thanks, > > -mka > > Michael Ackerbauer > SP System Test Sounds like you have a good handle on everything. The rule of thumb that I have learned form the classes I have attended is basically what you have stated. Move your physical and logical logs out of rootdbs. That will speed things up considerably. Dont put rootdbs on the same drive as the operating system. If you will be using index's, rebuilding them often, or they are very large then try to keep the temp spaces off of the drives that has the index spaces for the reason that when you build your indexes you will be using the temp spaces. If they are on the same drive you will thrash it. Separate your data from the index of the data to different drives. Make rootdbs larger than the default (we use 40k) to avoid the possibility of additional root chunks in the future. Calculate the extent sizes for you data and avoid more than 8 chunks It starting to sound like you need a different drive and controller for every dbspace. In Utopia we would have the $ for the hardware but since we dont you start high and work your way back. I am open for input. Hope it helps -----------== Posted via Deja News, The Discussion Network ==---------- http://www.dejanews.com/ Search, Read, Discuss, or Start Your Own
what is essential, if you ask me is to separate the logs form the root even across physical devices, of all the core database facilities, the logs get the most utilization, so having these on there own disk would be optimal. Here at The Sporting News, we have this configuration: SGI Origin 200 1 CPU 3 4GB SCSI disks disk layout: d0 -> root filesystem d1 -> datadbs1, rootdbs d2 -> datadbs2, physdbs (Physical logs) notice that we separated the logs from the rootdbs on separate physical media, Informix seems to think that you gain performance this way. The problem that we have is that the physdbs is not alone on a disk somewhere, but we don't appear to take too big a performance hit from it. As far as I can tell, you can put the rootdbs and anything else on one disk, put the logs and anything else on another disk, and you'll be OK, I've also heard that people make out just fine with one raw disk for the whole database environment. You can evolve this, you know, you can set up initially one way, and move things around, do it carefully (I'd break it a few times before you have any data on it) but it is possible. David ackerbau@us.ibm.com wrote: > > More questions on my home system. > > The scenario: > > Pentium 90 > 32mb RAM (eventually upgrading to 64) > 1.6Gb IDE hd > 4Gb SCSI hd > 2-1Gb SCSI hd's > SCSI CD-ROM > SCSI Tandberg tape drive > 2 SCSI controllers > > SCO Openserver 5.05 > Online 7.3 UC? (unsure of the release > ) > > My plan is to install the OS on the IDE drive, and split up the SCSI > devices across the two controllers. All the SCSI drives will be raw > device. > > I'm wondering what the best approach is to setting up the root, temp and > logs dbspaces relative to the data. I'm initially planning on the rootdbs > being on one of the 1GB drives, the logs on the other, the data spread > across all three drives. No striping planned, though I may mirror at > least the rootdbs. OLTP database(s), capacity unknown just yet; probably > ~ 100Mb to start. > > Am I missing anything obvious? Any generally accepted rules of thumb > appreciated. > > Thanks, > > -mka > > Michael Ackerbauer > SP System Test -- David Buttrick http://www.sportingnews.com WEB Database Specialist The Sporting News buttrick@sportingnews.com S E E A D I F F E R E N T G A M E