| || |
Webload virtual users vs actual users
As I understand webload agendas communicate with the HTTP server using Get and post commands. So this means that it is actually communicating with the Http server from the middle tire. How is this type of interaction different from actual users ascessing the website through a user interface in a browser.
Re: Webload virtual users vs actual users
The major differences are probably due to client-side scripts. WebLoad does not simulate a browser, so all client-side activity will not be performed or measured. This means that if you have some very heavy computations on the client such as a CPU-intensive applet or very complex html, the response times your users experience will be much worse than the measurements WebLoad gives.
One real-life example: We loaded a 6 Mb report that used a lot of tables - it turned out that the browser spend more time actually rendering the page than downloading it. However, WebLoad only measures the download time.