A few years ago, I worked a performance project. You probably know the type: Customers were upset, executives were upset, technical staff were asking for specific direction (and not getting much) … nobody was happy. The code was already in production, and there was no obvious ‘roll it back to the previous version that is
If you’ve done any performance testing, or even seen a demo, you are probably familiar with the “big line graph” that is created as the test runs. A Typical Response Time Graph The typical scenario is simple: Have the load tool start with one simultaneous user running a script. Then add a new user, say, every thirty
Intelligent Session Recording for Citrix and Calabrio
Subscribe to our newsletter
Get the latest from the world of automations.