Hi abdomin25,
I made some tests and think that the round trip time measures the overall runtime of the monitor,
and the time you only see in the monitor status actually shows the time the query execution took.
long startTime = PlatformNew.timeMillis();
// Execute query
results = executeQuery(path, fileQuery, query);
totalTime = PlatformNew.timeMillis() - startTime;
..
String duration = TextUtils.floatToString(((float) totalTime) / 1000, 2) + " sec";
..
summary = duration + ", " + rowNumber + " " + rowLabel + ", " + resultBuffer;
..
As we use different scales and roundings, it is hard to see it for small numbers.
Here are some examples from my boxes running a DB Query monitor against Oracle or MS SQL:
Database Query 0.003 sec, 1 row, sov02bac14, 15950
round trip time Status: 0 sec
-> round trip time is only represented with two digits,
thus 0.003 would be rounded to 0.00, as long as the round trip time is not > 0.004
Database Query 0.006 sec, 1 row, sov02bac14, 15950
round trip time : 0.01 sec
-> as above, but now the rounding results in 0.01 sec
For another box I even get 0 sec for the query time, and 0 sec for the round trip time,
which means that the database query execution time is below 0.005 sec, and the
round trip time as well.
In your case the query execution time is 0.016 sec
the round trip time is 0.02 sec, which can be anything between 0.016 and 0.024
Assuming that I'm correct you should never see that the time in the status (database query execution time) is larger than the round trip time
Greetings
Siggi