Archives of the TeradataForum
Message Posted: Mon, 24 Apr 2006 @ 09:39:04 GMT
We are running a mload script that uses INMOD routine. This mload process around 25,000 files having file size ~5MB and ~15000 records in each file. INMOD routines processes each file and apply some lookup operations and load these files into the staging table. This staging table keeps 15 days data in it.
Ours was a 8 nodes system which got upgraded into 18 nodes (36 PEs, 190 AMPs). This activity happened in two phases. In first phase, old 8 nodes were replaced with 10 new nodes and in second phase the old 8 nodes were added back to the system. We found major performance degradation on this particular Mload (that uses INMOD) after these two activities.
- When the system got up after phase-1, all Mload where SESSIONS were not specified started failing. Only after specifying the number of session within the script, MLOAD scripts started working. Can anyone tell me what could be the reason behind this?
- Secondly, this particular Mload already had SESSIONS defined in it (=32). So this didn't failed but it's performance went down significantly. earlier it used to take around 3-4 hours, but after phase-1 it started taking 7-8 hours. Moreover, this performance further went down when the system got up after phase-2. Now it's taking around 10 hours. Everything else is same in the environment. scripts are running on the same ETL box. We tried increasing the number of sessions but no improvement, moreover it's throwing error if no of sessions are more than 64.
Can anyone suggest what could be the possible reasons/solutions for this issue.
Thanks and Regards,
|Copyright 2016 - All Rights Reserved|
|Last Modified: 27 Dec 2016|