Bad Performance – Meaningful assessment of response-time data


I published on article on evaluating response time measurements for the September 2011 issue of “Javamagazin”. It is in German and available in print only (for reference, please follow the link http://it-republik.de/jaxenter/java-magazin-ausgaben/Enterprise-Javascript-000463.html).

Often we start performance improvements much too late in projects. This article explains how important it is to measure the response times of your software – already throughout development, and how you can create meaningful information out of the data gathered. In particular this means:

  • Establishing clusters of services/functions with excellent, very good, good and bad performance
  • Recognizing trends of potentially bad performance, i.e. services/functions that are performing well but show signs of performance issues
  • I packed the entire approach into a six repeatable steps, which can – most importantly – also get automated if you wish – for example – to embed them into your continuous build and deployment process

Copyright © 2011 Michael Pichler

Advertisements

2 thoughts on “Bad Performance – Meaningful assessment of response-time data

Leave a Reply

Fill in your details below or click an icon to log in:

WordPress.com Logo

You are commenting using your WordPress.com account. Log Out /  Change )

Google+ photo

You are commenting using your Google+ account. Log Out /  Change )

Twitter picture

You are commenting using your Twitter account. Log Out /  Change )

Facebook photo

You are commenting using your Facebook account. Log Out /  Change )

w

Connecting to %s