From the Blogosphere
Digital Performance Management | @DevOpsSummit #DevOps #Microservices
The easiest way to run a known transaction end to end from the user device to back-end services
By: SOASTA Blog
Mar. 15, 2016 12:30 PM
Meet the Three Musketeers of Digital Performance Management: Real, Synthetic and Virtual Users
Alexandre Dumas’s classic portrayal of a young man seeking to join the elite guard of his day seems an unlikely source of inspiration for a blog post about digital performance management, but there’s something about groups of three — each balancing the others’ strengths and weaknesses — that makes a great team.
And, while most operators today might view digital systems monitoring in terms of two players — synthetic and real users — there is a third member of the team that turns performance monitoring into performance management: the virtual user.
What does each user agent represent?
To understand how real, synthetic, and virtual user agents complement each other, it’s critical to understand what each represents. Sorting out why one might need both synthetic users and virtual users, for example — or even what the difference between the two might be — can be quite confusing.
Here’s a useful guide to the three user types.
Real users allow you to measure what the end user actually experiences through their front end stack (browser or app, OS, etc), but at the cost of being able to control the conditions in which the user is running those stacks. Being able to capture anomalies quickly, especially for things like key transactions or usage under exceptional loads requires the ability to collect data with more known initial conditions or baselines.
Unfortunately, because these systems don’t scale well, and these synthetic users can themselves affect performance if they generate too much load, these users don’t scale well at all. So, how do you create a baseline of expected behavior on the backend systems that have to scale to meet customer demand when stressed?
Virtual users can also be run at incredible scales during scheduled load and stress tests. Their initial conditions can be closely controlled, though the combination of scale and control of conditions comes at the cost of driving load primarily against the backend, without driving actual browsers or mobile applications.
How virtual users complement real and synthetic users
As our CEO, Tom Lounibos, is wont to say, cloud testing introduced the concept of load testing actual production systems, instead of focusing only on “staging” environments before release to production. This is a powerful concept for today’s rapidly evolving digital applications, but it’s only possible if the load testing system is capable of dynamically adjusting load from an extremely light baseline to a massive peak load without rebuilding the load tests.
The way SOASTA achieves this is by utilizing CloudTest to drive virtual users through the system at a load that can be adjusted throughout a test run as needed. So you can choose to either run “baseline” tests as separate tests from time to time, or continuously run a load test that can be throttled up and down as needed over time.
Low levels of testing give you a baseline of behavior for these test users, which can be compared to behavior when the throttle is turned up. (Low level tests are also great for finding code changes that negatively affect performance or break the load test scripts before a critical load test finds them first.)
This comes at the cost of not using actual browser and device profiles, of course. You won’t know from a virtual user if the experience is better in Chrome or IE, for instance, from a virtual user in a load test. However, you will be able to confirm that your backend servers can handle any anticipated (and all but the most unimaginable unanticipated) loads when they come.
How real and synthetic users complement virtual users
Example 1: Real user monitoring data will tell you a lot about the situation that cost you the most in terms of whatever your conversion metric might be
Sometimes the situations that cost you the most aren’t obvious. We’ve seen situation in which specific product pages had serious conversion issues, though not all such pages did. Real user data can make that clear, and then load tests can be created to test that condition, at least until you’ve confirmed the problem no longer exists. (Even then you can run the test occasionally as a form of regression testing.)
Example 2: Using the virtual user baselines noted above as additional baselines for real and synthetic user measurements
Does your backend perform differently under varying loads? When is a real or synthetic measurement truly an anomaly vs expected (though not necessarily “acceptable”) behavior? Having a strong, controlled profile of your system performance gives you greater confidence in tagging events as unexpected versus expected.
With this combination, you have the makings of a complete picture of where, how, and why performance affects user outcomes.
And understanding user outcomes enables understanding both business and technical outcomes.
Latest AJAXWorld RIA Stories
Subscribe to the World's Most Powerful Newsletters
Subscribe to Our Rss Feeds & Get Your SYS-CON News Live!
SYS-CON Featured Whitepapers
Most Read This Week