Here is some information I had in another thread:
Disclaimer I'm not from the Automic side but I was curious so decided to run a DB4 trace on a start up of a WP and here is what I saw.
SELECT DIVDB_String, DIVDB_Date, DIVDB_Memo FROM DIVDB where DIVDB_PK = 1
INSERT INTO DIVDB (DIVDB_PK,DIVDB_Memo,DIVDB_String,DIVDB_Date) VALUES(1, ?, ?, ?)
SELECT DIVDB_String, DIVDB_Date, DIVDB_Memo FROM DIVDB where DIVDB_PK = 1
The INSERT shows in the startup 1000 times and the SELECT shows up 2000 times.
Bind parameters however is just Umlauts for every field: öäüÖÄÜß{}[] (that exact string from trace >öäüÖÄÜß{}[].....<)
Another thing I found interesting is that it looks like it runs 1000 insert statements regardless of how long it takes. For example here is the results from my startup
CPU/DB: '28209746'/'221 (1000/4.506597 s)
So it took 4.5 seconds to run all 1000 inserts. Its not done by going lets see how many we can do in 1 second. I runs it 1000 times and then divides it how by long it took.
Lastly, the data is then truncated.
Original Message:
Sent: 08-29-2017 03:27 AM
From: Michael Lowry
Subject: Message queue lengths
In a recent incident, Automic analyzed traces using another similar tool:
Reading E:\temp\4\WPsrv_PROD_trc_001_00.txt ...
U00003492 Server has been started on Host 'myhost1' ('192.168.0.1') with process ID '12345'.
Primary: True RWP: False OWP: False DWP: False
Transactions: 2.010
Transaction Time (ms): 189.731 Average: 94,3935
AE Time (ms): 30.400 Average: 15,1244
DB Time (ms): 159.331 Average: 79,2692
Ratio Database:AE 5,24:1
Dat_Nguyen-Tat_9196: Have you seen my request above? We would appreciate it if you could provide instructions for analyzing the trace files - or better yet, the tool you are using to process the data.
We would also like to have copies of the exact SQL statements the Automation Engine is using to measure DB performance. This way, we can run these statements outside of the AE to verify the results. Thanks in advance.