Proactively Avoid Site Abandonment by Identifying Thread Contention Issues

Lucy Monahan, Principle QA Performance Engineer at Novell, approached this with the following problem proposition:

Imagine that you go to a shop to buy something and instead of customers lining up one-by-one, sequentially, each one vies for the shopkeeper’s attention. And imagine that you arrived as customer #2 and the shopkeeper takes one or more other customers before you. How long would you wait?

Consider this somewhat exaggerated scenario and extrapolate it to shopping on the web. Could a similar phenomenon be happening to your customers? How long will your customers wait before they give up?

In her blog she walks through the process of analyzing and solving thread contention
In her blog she walks through the process of analyzing and solving thread contention

Read the full post that outlines a way of detecting this possible site abandonment scenario


Andreas Grabner has 20+ years of experience as a software developer, tester and architect and is an advocate for high-performing cloud scale applications. He is a regular contributor to the DevOps community, a frequent speaker at technology conferences and regularly publishes articles on blog.dynatrace.com. You can follow him on Twitter: @grabnerandi