Re: Update Statistics Speedup Help???

--------Greg wrote: > > You The Man Art - exactly what I was looking for - I knew you would have > it well doped out. David - this looks like it will be a good candidate > for the FAQ soon. > I do have a couple of questions: > 1. According to the 7.1 doc, PSORT_NPROCS max thread value is 10 - what > is the effect of setting it very large?? Don't believe everything that you read. The larger PSORT_NPROCS the more sort memory block and sort threads are allocated. Menlo still insists that it ain't happening but try the same index build with the same PDQPRIORITY and different PSORT_NPROCS and watch with onstat -g ses <sid> and you tell me what good it does. I've done the testing, but like every good scientific investigation it needs to be duplicated by others. I have thrown down the gauntlet... > 2. What is PSORT_MAXALLOC - I can't find any doc for it. It is the size of the in-memory sort blocks in KB. While I do not believe for an instant that PSORT_MAXALLOC=10240 actually allocate a GB of sort memory, things do test out to run fastest with this value which is the maximum value. Don't ask how I know about this one, sometimes I poke my nose into places where it don't belong, OK! Suffice it to say that PSORT_MAXALLOC is undocumented. > Thanks for the tip about the ontape/onbar bug - I hadn't been bitten by > it yet.... Your welcome. Art S. Kagel