I am having web based application scripted using web(http/html) protocal.
Manaully application takes 9-10 secs to complete transaction . Even through vugen it takes time
but we have observed through BPM it runs everytime in 2-3 secs . What could be the issue as customer is not agree
We have raised support case as well and as per support this is normal behavior .BPM always give faster response than vugen and manual login
Vugen and bpm installed on same system .
Yes, we have observed the same and the support team also says it is common behaviour.
This is not a problem, but a very expected behavior:
Browser time effected by rendering time, and client time.
Vugen behavior - effected by IO time, and IDE time (logs, internal processes)
BPM- measure only network time, it does not render like browser.
in order to be more close to browser behavior , you must use TruClient protocol, and not HTTP/web protocol
if cusomter is interested to find server availability issues, HTTP/WEB will capture server errors
If customer is interested in check ISP network issues, HTTP/WEB will do the job
if cusomter is looking to measure rendering time, and browser behavior on OS + network - TruClient is the best feet
Thanks for response
I see diffenrence of 10-20 secs between BPM and others
Also BPM shows client time , netowrk time to first buffer , server time to first buffer etc ? HOw it captures than
As we always simultaing robotic transactions and captures response. No where in HP database it is document ?
Read this section of the BSM User Guide:
Understanding Transaction Breakdown in Reports
It provides details of how transaction breakdown is calculated and what each part is measuring.
i still not convinced
no where it is documented hp bpm gives faster response time for transaction monitoring
Honestly, I'm not sure what else is not clear.
BPM measure network time only for HTTP/web protocol
Vugen is not a tool to measure response time
IE measure network + client
BPM client time (breakdown) is not rendering time, but total time - network time - meaning it should be 0 most of the times. if it is not almost 0, it is not good.
The differences that you described, are according to the expectations. You have to look at the trends when using HTTP/web protocol.