IBM Support

Repository View THROUGHPUT_CONNECTION

Question & Answer


Question

Repository View THROUGHPUT_CONNECTION

Answer

Usage

 

Source

 

Columns

As with all repository views, the columns marked Y in the “Delta” column are actually two columns.  For example, the metric described here as “rows_read” is actually a pair of columns “rows_read” which is a counter of how many rows have been read by activities since the data server was activated and “rows_read_delta”, which tells how many rows have been read by activities in the collection interval.  For most purposes, the _delta version of the metrics is the most useful.  The raw counter version is provided for completeness.

Column Name

Delta

Type

Description

dbconn_int

n

integer

 

dbconn_id

n

varchar(255)

 

prev_collected

n

timestamp

 

collected

n

timestamp

 

delta_msec

n

bigint

 

application_handle

n

integer

 

total_cpu_usec

Y

bigint

Microseconds of CPU time consumed by the data server.  Divide by 1,000,000 to scale this as seconds.

CPU consumption is a good indication of how much work is being done. 

All activities, including overhead such as compiling queries and utility work are reflected in CPU consumption. 

Inefficiencies that increase the cost of doing business, such as excessive recompilation or lock contention can sometimes be seen by observing that CPU consumption has risen disproportionately to the amount of useful work that is being accomplished.

act_completed_total

Y

bigint

Activities completed by the data server.

Activities typically correspond to a query.

The number of activities completed is a measure of work accomplished.

rows_read

Y

bigint

Rows read is a good indication of how much work is being done by queries. 

Non-query work such as utilities and overhead for internal activities of the data server is largely excluded from rows read.  So it is a better measure than CPU time for evaluating how much useful work is being accomplished.

rows_modified

Y

bigint

Rows modified includes updates and deletes of table data.  Modifying data is much more expensive than reading it.

rows_returned

Y

bigint

This is the number of rows returned to the client by queries. 

Excessive amounts of data returned to the client can indicate a run-away query (cross product, missing filters) or abuse (people in the process of making unauthorized copies of the data) or even bad practices such as mis-guided attempts to pull large portions of the data into a spreadsheet or an application for post processing that could be better done inside the server.

logical_reads

Y

bigint

 

direct_reads

Y

bigint

 

direct_writes

Y

bigint

 

total_sorts

Y

bigint

 

total_app_commits

Y

bigint

 

total_commit_time

Y

bigint

 

total_app_rollbacks

Y

bigint

 

act_per_second

n

double

 

connection_start_time

n

bigint

 

ext_table_send_volume

Y

bigint

 

ext_table_recv_volume

Y

bigint

 

application_name

n

varchar(128)

 

 

Example --

[{"Product":{"code":"SS5Q8A","label":"IBM Data Server Manager"},"Business Unit":{"code":"BU059","label":"IBM Software w\/o TPS"},"Component":"--","Platform":[{"code":"PF016","label":"Linux"},{"code":"PF033","label":"Windows"},{"code":"PF002","label":"AIX"}],"Version":"2.1.3;2.1.2;2.1.1;2.1;2.1.4;2.1.5","Edition":"","Line of Business":{"code":"LOB10","label":"Data and AI"}}]

Document Information

Modified date:
31 December 2019

UID

ibm11166488