We have a simple http operation (a post followed by an http 200)
We often see very high idle times (up to 90% of the operation time)
How is this idle time calculated?
Reading the documentation, I understand that this is the time where no client requests are seen (meaning the client is idle)
However in this case there is only one request/response?
I did understand idle time like that indeed
I only don't see why it reports idle time on an task consisting of a single post-reponse (no multiple objects)
POST https://intrauat.web.bc/shem/salto-p-enu/start.swe HTTP/1.1
User-Agent: Mozilla/5.0 (Windows NT 6.1; rv:34.0) Gecko/20100101 Firefox/34.0
Accept-Encoding: gzip, deflate
Content-Type: application/x-www-form-urlencoded; charset=UTF-8
HTTP/1.1 200 OK
date: Mon, 23 Feb 2015 15:53:46 GMT
p3p: CP="NON CUR OTPi OUR NOR UNI"
I am curious how this would be for DB, and specifically Oracle DB
I sort of get it for HTTP. That it is the time from the last packet is acked until the next "expected request" is sent.
But how would this look in a DB scenario? Is it whenever a response is split up in several parts?