IDS 9.20 on HP-UX 11.0, 3cpu vps, 6 physical cpus.
What's the view on trying to optimise index builds these days?
I ran some builds on a 28 million row table. About 3 hours per index, cut
down to 45 minutes when setting
PDQPRIORITY=100
PSORT_TEMP to some file systems
PSORT_NPROCS=24
I admit that I'm not certain that the fast indexes had as many columns as
the slow, but am still interested to know others' views.
↪ replying to Neil Truby
In the year of Our Lord Wed, 31 Jan 2001 22:19:14 -0000, "Neil Truby"
<ntruby@netcomuk.co.uk> spake, saying:
>IDS 9.20 on HP-UX 11.0, 3cpu vps, 6 physical cpus.
>
>What's the view on trying to optimise index builds these days?
>
>I ran some builds on a 28 million row table. About 3 hours per index, cut
>down to 45 minutes when setting
>
>PDQPRIORITY=100
>PSORT_TEMP to some file systems
>PSORT_NPROCS=24
>
>I admit that I'm not certain that the fast indexes had as many columns as
>the slow, but am still interested to know others' views.
PSORT_NPROCS does vary, I've gone up to 32 on an 8-way box. I set PSORT_DBTEMP
to 5 filesystems. Index builds are now take about a third of the time than with
"sequential" processing.