Re: Temp DB space question

If you have multiple temp dbspaces, you need to take special care in regards to the size of the 1st temp dbspace listed in the ONCONFIG. Online has a bug in that during an Index build, if the 1st temp dbspace was not the same size as the others, it assumed that the size of the 1st temp dbspace was all the space it had to work with and would internally recalculate based upon the limited resources and continue. This resulted in a single-threaded index build. Informix Bug 83745. Neil Truby wrote in message <6tt5js$bnb$1@taliesin.netcom.net.uk>... > >Raghava Ponnapalli wrote in message ><01bde2a4$aa0f8660$6500430c@pcrponna01R.osg.eds.com>... >>Hello everyone, >> >>What is good size for temp db space (Other than "depends on queries"). We >>have tempsp1,tempsp2,tempsp3. When tempsp1 gets full, does Informix >>automatically use tempsp2 and then 3. Should I combine them into one ? >>Thanks >> >>Keith > >Depends on queries of course! As a vague rule I usually initially size >tempdbs to be about 10% of the sum of the application dbspace(s), but this >really next-to-meaningless, because it does really depend upon your >application. > >The engine populates each tempdbs as it goes; e.g. in your case a large sort >will use tempsp1,2 and 3 in parallel, filling them in more-or-less equal >proportions as it goes. It follows that by combining them into a single >space removes the element of I/O balancing across the spaces that this usage >algorithim provides. > >Neil Truby >Londis Holdings >Hampton Hill >London, UK > > >