Send feedback on this topic.
Teradata.Client.Provider
Performance Counters
.NET Data Provider for Teradata > Developer's Guide > Performance Considerations And Best Practices > Performance Counters
.NET CORE   This feature is not supported by the .NET Core implementation of the Data Provider.

The .NET Data Provider for Teradata updates performance counters while your application is running.  These performance counters may be helpful in understanding your application behavior and performance.  The easiest way to use these counters is to start your application and bring up the Performance Monitor.  The counters are added using the Add Counters option in the Performance Monitor.  The performance counters are available under the Performance Object listed as the “.NET Data Provider for Teradata”.  Once the “.NET Data Provider for Teradata” is selected, the list of available performance counters will be displayed, along with the available instances for monitoring.  If your application is running you should see the application process name and can choose that instance for monitoring.   Multiple concurrently running applications with the same name (e.g. myapp.exe) will share the same performance counter instance.  In addition, the _total instance can be selected, which is maintaining total counters for all concurrent applications that are using the .NET Data Provider for Teradata.

The following performance counters are available for monitoring:

Performance Counter Name Description
Number of Connection Pools This counter indicates the number of connection pools created for the application process.  Connection pools are created for each unique connection string that has the CONNECTIONPOOLING parameter set to true.  Connections are then maintained in the connection pool.  Idle connections within a connection pool are released over time, but the connection pool itself is never released.  Therefore, while the application is running, this counter will not decrease.  The counter is finally removed when the application terminates.  The _total instance indicates the total number of connection pools created across all currently running processes.
Number of Connections This counter indicates the number of active connections currently in use by the application process.  This includes both pooled and non-pooled connections.  This counter is incremented when a new session to Teradata is opened and decremented when the session is closed.   This counter is helpful in determining the connection usage by the application.  In situations where the number of connections continues to rise, the application may be leaking connections by not closing connections when appropriate.   The _total instance indicates the number of active connections across all currently running processes.
Number of Open Connection Requests This counter indicates the number of open connection requests per second made by the application process.  This counter is incremented whenever a connection request is made.  The connection may come from a connection pool or a new connection may be created.   This statistic may be useful in determining the correct size for the pool.  If more connection requests per second are made that the current pool size, it may be worthwhile to increase the minimum size of the connection pool.   If fewer requests are coming in per second than the current minimum size of the pool, the minimum connection pool size can be lowered.  This counter is averaged over the time period selected for monitoring.   The _total instance indicates the number of open connection requests per second across all currently running processes.
Number of Pooled Connections This counter indicates the number of active connections in all connection pools associated with the application process.  The counter is incremented when new connections are created and added to the connection pool.  As idle connections are released from the connection pool, the counter is decremented.  This statistic is helpful in determining the appropriate size for the connection pools and determining minimum and maximum connection load demanded by the application.  The _total instance indicates the number of active pooled connections across all currently running processes.