Link Details

Link 949409 thumbnail
User 394588 avatar

By skruk
via apmblog.compuware.com
Submitted: Apr 03 2013 / 13:47

When we set up our application performance monitoring tool to correctly notify us about unexpected performance degradation, we often know about problems before our users start making calls to support. But what happens when we actually learn about a major performance outage? Psychologists identified two ways people falter under pressure. Some people choke: they revert to over-cautious, slow procedures they used when learning new things. Other people panic: their perception gets dangerously narrowed towards one potential cause of the problem and they lose the bigger picture. But when you are experienced enough, and have defined the standard operation procedures to ensure proper resolution of the problem from the end user perspective, you will neither choke nor panic. Just like one of our customers whose story I detail in this article.
  • 5
  • 0
  • 211
  • 9

Add your comment


Html tags not supported. Reply is editable for 5 minutes. Use [code lang="java|ruby|sql|css|xml"][/code] to post code snippets.

Voters For This Link (5)



Voters Against This Link (0)



    Reactive Programming with Akka
    Written by: Ryan Knight
    Featured Refcardz: Top Refcardz:
    1. Design Patterns
    2. OO JS
    3. Cont. Delivery
    4. Java Performance
    5. HTML5 Mobile
    1. Java Performance
    2. Node.js
    3. Debugging JavaScript
    4. Java
    5. Java Concurrency