runres

NAME
DECLARATION
COLUMNS
NOTES
COPYRIGHT
SEE ALSO

NAME

runres − RWP*Load Simulator runres table and runres_a view

DECLARATION

When using the -s option and a results database, the runres table saves overall execution statistics of the execution of all procedures doing database work or having the statistics attribute. The runres_a view aggregates results from a multi process run.

create table runres
( runnumber number not null
, procno    number not null
, vname     varchar2(30) not null
, wtime     number(*,6)
, etime     number(*,6)
, atime     number(*,6)
, dtime     number(*,6)
, ecount    number
, tcount    number
, constraint runres_pk primary key(runnumber, procno, vname)
)

create view runres_a
( runnumber
, pcount
, vname
, wtime
, etime
, atime
, dtime
, tcount
, avgw
, avge
, avga
, avgd
, ecount
)

COLUMNS

runnumber

This is the number that uniquely identifies a run.

procno pcount

In single process runs, procno is zero, in multi-process runs, it gets its value from the Operating System process number of from the -p option to rwloadsim. In the aggregate view, runres_a, the total process count is in the pcount column.

vname

This is the name of the procedure being executed.

wtime

Total time in seconds spent waiting to get a session from a session pool. For a dedicated database, this time can be positive if a control loop uses queue every and the $queueeverytiming:on directive is used.

etime

Total time in seconds spent executing the code in the procedure, not including time used to get a session.

atime

When the $statsapptime:on directive is used, the time spent executing OCI calls that interact with the database will be measured. The total time spent using such calls effectively is time spent outside your rwl program, and that total time is subtracted from the value saved in the etime column and saved in the atime column. Effectively, the atime column therefore is the time spent executing application code. There is some overhead in measuring this time, and if no $statsapptime:on is used, a value of zero will be stored in the atime column.

The current list of calls where this time is measured is OCIStmtExecute, OCIStmtFetch2, OCITransCommit, OCITransRollback, OCIPing and OCI calls that deal with reading and writing lob data.

dtime

When the $statsdbtime:on directive is used, OCI_ATTR_COLLECT_CALL_TIME is enabled and measured for the OCI calls mentioned above under atime. The sum of these times is subsequently saved in the dbtime column. This time effectively represents the database time spent by your rwl program. There is some overhead in gathering this time, and if $statsdbtime:on is not used, a value of zero will be stored in the dtime column.

ecount

Total number of executions of the procedure.

tcount

Number of threads having an execution of this procedure.

avgw, avge, avga, avgd

Average time spent waiting for a session, executing the procedure, execuring application code respectively database time.

NOTES

At present, the atime and dtime columns only contains values from executing the OCI calls mentioned above under the description of atime. The implication is that the atime and dtime columns only are correct if your procedures do not call other procedures using a stacked at clause. This may change in some future release.

COPYRIGHT

Licensed under the Universal Permissive License v 1.0 as shown at https://oss.oracle.com/licenses/upl