Archives of the TeradataForum
Message Posted: Tue, 24 Feb 2004 @ 16:15:15 GMT
We are running an antique 4-node, 32 amp, 4700 with Pentium 200 Pros (built about 1997) and still at V2R3.
There was no Multiload when we began years ago (Bulkload was too slow), so we strictly ran Fastload utilities and do so today. Our batch jobs from the mainframe typically consist of a COBOL unload program, a Fastload, then SQL batch scripts. Many of these jobs have 20-60 of these activities mixed together.
The manipulations that normally occur in Multiload are built into our COBOL unloads or in the batch scripts. We let the mainframe do those manipulations it does best, and Teradata do those manipulations it does best.
With our mix of only fastload utilities, we usually coast with about 6-8 Fastloads simultaneously, but do on occasion hit the magic number of 15 without any problem. Perhaps we are fortunate to have a skew rate at less than 3% so we have our amps pumping at top speed. We probably run anywhere from 100 to 400 Fastloads nightly.
We started with (5)five fastloads and then gradually increased that number watching/recording run times as an intial barometer of thru-put. Of course run times are different at night when most of our users are off the systems. We are careful of pre-requisites so that we spread our jobs over databases both on the mainframe and Teradata and avoid i/o contention, locking, etc. At the same time, we are doing backups with NetVault and once in awhile we get a lock conflict, so that's another consideration.
there have been a number of threads on this subject before and I think the general concensus has been to start small and increase gradually til you find your optimum mix of variables.
John Balchunas Jefferson County Public Schools
|Copyright 2016 - All Rights Reserved|
|Last Modified: 27 Dec 2016|