Re: HPL Deluxe Mode

In article <09dc15af.2e43de16@usw-ex0104-028.remarq.com>, rboscia <rbosciaNOrbSPAM@ems.att.com.invalid> writes >I have never used HPL before last week. Last week we used >Express Mode and our data locked up during the indexes. >Informix suggests building indexes after the load which we >tried this week. The data unload/load took 1.5 hours. The >indexes took 13+ hours and only 4 of the 6 are done. Obviously >with users not able to access the data for that long of a time, >I don't want to go that route again.... > >So I think I will try Deluxe Mode next time at least for this >table... > >Since I still have 2 more indexes to go and my table has been >locked forever, could you tell me more about PDQPRIORITY and >PSORT_NPROCS? >We are running 7.31 UC5 on Sun Solaris 7 E10K machine Drool...how much memory, how many/what CPUS? What is the disk layout (number of disks/size of disks/disk to controller mapping/RAID levels/mirroring)? With 100 million rows how is the table fragmented? How are you using temporary dbspaces/ PSORT_DBTEMP? Allocate one temp space per drive. > Go with PDQPRIORITY=100 which Art and Mark D. Stock have suggested. Under Solaris 2.5.1/2.6 with a Ultrasparc 1 170Mhz and Various E450's I have seen improvements by increasing PSORT_NPROCS > number of physical cpus. PSORT_NPROCS= 2 x number of physical cpus is as far as I have tried to go and it scaled almost linearly!! >Thanks >Robin > > >Got questions? Get answers over the phone at Keen.com. >Up to 100 minutes free! >http://www.keen.com > -- David Williams