0 - 5 of 5 tags for resusagespma

I would like to ask you about the DBC.ResUsageSpma Table and the performance of the Teradata.
We have a Teradata 2800 with 2 Nodes and we are having some performance issues. When I take a look at the DBC.ResUsageSpma the results the attached.
Is something wrong with Node ID 105?.
Thanks in advance.

Hi all. We're working on creating operational reports to measure key metrics for Teradata 13.10. We typically use DBQL/Acctg to report on users and ResUsage tables for platform-wide metrics.

This is just a quick note to put some information out here to see if it helps you to more easily create charts from the Resusage data.

Much of the information you should be tracking comes from DBC.ResUsageSPMA, and that is what this process is going to analyze. Note that this process is for TD12 only.

In ResUsageSpma data is reported per node. The definition of column AwtInUseMax is given as:

Peak number of AWTs (Max) on this node. This
is not the Peak or the Max value stored in the
Priority Scheduler (sch) data structure and
reported by the puma utility. The sch peak value
is the Max value since startup is never set and
Max is the maximum allowed value.

We don't know if this gives us the maximum AWT count from all the AMPs in the node
sum of maximum AWT count from all AMPs

From Teradata documentation, the definitions of these ResUsageSpma columns are:

FilePres Total number of times a cylinder is loaded.

FilePreReads Number of times a cylinder is loaded.

which look similar, but I observed on our lab's Teradata and found quite different values with an observation that:
FilePres = 2 x FilePreReads (approx.)

I also looked into KA but couldn't find any explanation. Please respond if you know the meaning of these fields.