1. We are experiencing big time differences between the Page Timers SP reports and the Custom Timers set around the page load. Has anyone else noticed this and is there a know issue/resolution?
The code looks as follows:
2. There is also big time differences between try script timings and simulation run timings. The Try script timings are larger that the simulation times. Is this due to animation?
3. There is time differences when run on OS:XP and OS: Windows Server 2003. Is this a know fact?
your timings, especially when settin up your manual measure times depends upon what it is you want to measure. Not sure about the XP Windows 2003 side but I would expect your server timings to be a little different dut ot the threads and also dependeant on what application etc is running on the server box itself.
Your try script timing is based on 1 VUser and not multiple VUsers when running the simulation hence the difference there.
As for the discrepencies you see between page load custom timers and default timings i am a bit puzzled. Could this be an agent/network/NIC card problem? it might be worth having a look
Ive just been checking a similar issue with the silk vision.
Here is what i found ...
The custom timers sums up the response times of all calls between MeasureStart & MeasureStop.
If you have several calls between the custom timers, the timer of each call needs to be exactly the same. i.e. if i record a script to login to a system ... it will be one step for me 'login' but there might be several requests to the server. So then i need to have the timer of each of the request to be exactly the same.
But the problem with the page timers on the requests is that the segue tool shows you the average of the response times. i.e. if you have 4 requests within the custom timer ... The page timer will add the response times of each request & divide it by 4 ... hence the difference!
There is a way within silkvision to get the total of the page timers rather than the average. This is done via a custom report where you need to write a SQL query. But Im not sure for silkperformer.