 |
 |
Archives of the TeradataForum
Message Posted: Tue, 09 Mar 2004 @ 22:56:13 GMT
Subj: | | Re: V2r5.1 Upgrade question |
|
From: | | Claybourne Barrineau |
Bhupesh,
Unlike CPU and IO, memory problems are harder to identify when they are actually happening. Via dbc.resusagespma, I can verify (after the
fact) that we had memory issues (i.e, a lack of it at certain times of the day.) However, I cannot quantify how these memory issues are impacting
performance (other than degraded query response times, log on times, etc.) I would recommend 4 gig per node if you are going to upgrade to V2R5;
however, I cannot provide you with a means to support the cost of this new memory.
Does Teradata factor memory into its mysterious T-PERF calculation? If so, I'd start there. If not, I'd question the T-PERF calculation.
Hope this helps,
Clay
| |