Archives of the TeradataForum
Message Posted: Sun, 02 Mar 2008 @ 10:56:05 GMT
Running 4 to 5 MLoads on a single node system will result in 100% system usage. The number of MLoad/FastLoad sessions can't be greater than the number of AMPs.
Fillers, large rows, VarText and Checkpoints might slow down the Acquisition, but not the Application phase. According to the posted log Acquisition phase was 30 seconds, but Application phase 30 minutes.
You export and MLoad? Did you try a simple Insert/Select instead?
UPI means no dup row checks
Stats will not change the runtime for any kind of insert/update/delete or MLoad an a table.
I'd guess that it's mainly because of:
1. parallel MLoads
2. loading just a small number of rows. Mload is only efficient, if the number of modifications per datablock is greater than 1.
417.665 out of 100.000.000 is just 0.42 percent, TPump (even BTEQ) might deliver better performance.
Is the target table partitioned? Loading into just 1 or a few partitions might speed up the load.
|Copyright 2016 - All Rights Reserved|
|Last Modified: 27 Dec 2016|