Skip to main content
Thursday, October 16, 2014 - 11:15am - 12:15pm
Continuous Delivery

Checking Performance along Your Build Pipeline

Do you consider the performance impact when adding a new JavaScript file, a single AJAX call, or a new database query to your app? Negligible, you say? I disagree―and so should you. Andreas Grabner demonstrates the severe impact small changes can have on performance and scalability. Many small changes will have an even bigger impact so it is important to catch them early. If you are working with a delivery pipeline, make sure to look into performance, scalability, and architectural metrics such as the number of resources on your page, size of resources, number of requests hitting your web servers, database statements executed, and log messages created. Monitoring these allows you to add a new quality gate to your delivery pipeline and prevents major problems. Andi shares a handful of metrics to teach to your developers, testers, and operations folks, and explains why they are important to performance.

Andreas Grabner, Compuware

Andreas Grabner has more than fifteen years of experience as an architect and developer in Java, .NET, and Web 2.0 with a strong focus on application performance. At Compuware APM (formerly dynaTrace) Andi is a technology strategist, helping companies improve their applications’ performance across the development lifecycle by embracing ideas of continuous delivery and DevOps. He is a frequent speaker on software performance, testing, and architecture topics at technology conferences including Velocity, STAREAST, STARWEST, and JavaOne.

read more