Teradata Manager

[craig322]

Has anyone seen any good documentation on teradata manager? I am looking for something that gives some baseline values for the information that you can get out of this tool? For example, what range should your Wait I/O be in (when viewed through the DUC performance tool)?

There are a lot of good tools, but I haven't found anything
that tells you how to apply the information you get out of them.

TIA

Craig

 

[tdatgod]

Hi,
Please don't shoot the messenger. TM is only reporting the numbers it gets from SAR. I would be very surprised if there was any discussion in the TM manual about what an acceptable value for these to be.

Wait I/O is a representation of how much time EVERY process on the system is spending waiting data from the disks.

In a perfect world we would never have to wait for I/O, But we aren't there.


Its possible that if you add indexes or collect statistics on certain columns that the optimizer will be able to generate less disk intensive Join plans.

We currently don't have a tool which can suggests indexes that would make a subset of queries run better. We are working on one but it won't be available until v2r5.

If you think the WAIT I/O is outside of what you consider reasonable Talk to your Teradata SSR and/or open an incident with the GSC.


The worst they will say is this is normal for your workload and you need a bigger system.

They might suggest upgrading to the latest release 4.1.

Both of these may require a capital out lay although not being a sales person I am not privy to know how much.

Sorry I have no silver Bullet but every system and query set is UNIQUE and being able to resolve the problems require intimate knowledge of the system and that is what we pay the GSC and professional services to do for us.



You might want to review our documentation at....

http://www.info.ncr.com/sd/sd-1.cfm

( which may currently be offline to avoid catching the NIMDA virus )

I think there is a document related to performance here as well as Client utilities like Teradata manager.

http://mahon.homeip.net/remember

 

[tdatgod]

Hi,
I should also point out that WAIT I/O is identical to IDLE except that it means that every running process is BLOCKED waiting for I/O so the CPU can't find any one to run and therefore the CPU's are IDLE, but not really.

If you had another task which wanted to use the CPU to do some CPU intensive work then you could use that time on the CPU while the other tasks are waiting for their I/Os to complete.

the amount of time this other task spent on the CPU will reduce the WAIT I/O value.