Queries the average number of transactions per second and the average number of transactions per second

Queries the average number of transactions per second and the average number of transactions per second
1. Directly query the view select * from DBA_HIST_SYSMETRIC_SUMMARY where metric_unit = 'transactions Per second'
METRIC_NAME metric indicator METRIC_UNIT Monitoring Unit INTSIZE sampling length (S), generally 361_num_interval observation interval (minutes), generally the AVERAGE value of 60 AVERAGE monitoring period


-- Query the average number of transactions per second within a period of time select instance_number, metric_unit, trunc (begin_time) time, round (avg (average), 2) averagefrom DBA_HIST_SYSMETRIC_SUMMARYwhere metric_unit = 'transactions Per second' and begin_time> = to_date ('2017-08-04 08:00:00 ', 'yyyy-mm-dd hh24: mi: ss ') and end_time <= to_date ('1970-08-08 23:00:00 ', 'yyyy-mm-dd hh24: mi: ss') group by instance_number, metric_unit, trunc (begin_time) order by instance_number; -- the number of DJI transactions is about 20-25 per second.
Query the average number of transactions per day over a period of time, as long as the average number of transactions per second * 60 ^ 60*24.
2. You can also query the AWR report.
3. -- The following script is executed at two time points, respectively. The number of times a user commit is obtained by subtraction, that is, the number of transactions in select s. USERNAME, sum (se. VALUE) "session transaction number", sum (sy. VALUE) "database transaction number" from v $ session s, v $ sesstat se, v $ sysstat sywhere s. sid = se. SID and se. STATISTIC # = sy. STATISTIC # and sy. NAME = 'user commits 'and s. USERNAME = upper ('& username') group by s. USERNAME;



Determine the maximum number of transactions per second for loadrunner

Each transaction is always composed of multiple clicks per second.
Total Trans/Sec = per Second Hits + Pages Downloaded + Connections + SSL
Therefore, the analyzer has the maximum number of clicks per second and the maximum number of transactions per second.
If you want to ask the number of clicks per second, when is the maximum throughput? Of course, when the server crashes and cannot handle such a large amount of data. You can refer to the number of current users of the crash.
Because of the number of clicks per second, the increase in throughput is caused by the increase in the number of users
For example, 100 users certainly have a larger number of clicks than 1 user.
The more pressure the user has, the more clicks per second, and the more transactions per second.
If it is a general performance test, the maximum number of transactions is reached when the performance requirement is reached.

How to analyze the loadrunner result to obtain the number of transactions processed per second

TPS is correct. But it also needs to be combined with your transaction definition.

In addition to the transactions defined in the script, the transactions include init, action, and end. In itself, one action (init, end) is also counted as one transaction. Action covers your custom transactions. Therefore, the statistics here are repeated. This is worth noting.