Top 10 Application Performance Problems

July 20 2015

A transaction is defined as one or multiple threads running in or across server boundaries on multiple runtime environments. And with today’s rapid enterprise growth, the demand for high-performance transactions through software run applications is higher than ever before, which means a greater need for these threads to be run on their respective platforms efficiently, and without delay.

Principal Sales Engineer, Hugh Brien, shares some of his findings on the common application problems discovered in transaction threads and the core concepts to think about while investigating issues to ultimately optimize the end user’s experience. Some of the main findings include server configuration in thread pools, identifying a correlation between load and response times to find request overloads, I/O bottlenecks, and improper memory configurations for transaction volumes. Hugh also walks us through strategies and measures specific to Java, .NET and more to further identify potential problem areas, and how APM exposes them beforehand.

Brien also spoke on what it takes to start constructing a defined process to understand a customer’s pain points, and further clarify the best practices on how to best utilize application intelligence and avoid future troubleshooting.

Browse through the deck today!

Top 10 Application Problems from AppDynamics

Saba Anees
Saba is the Content Marketing Specialist at AppDynamics. She grew up in the SF Bay Area, graduated from UC Berkeley, and joined AppDynamics' Marketing team in 2015. You can follow her on Twitter at @sabaanees.

Thank you! Your submission has been received!

Oops! Something went wrong while submitting the form