Session338.2Botelho

8/2/2019 Session338.2Botelho

1/8

Apdex: Your Compass forApdex: Your Compass for

Application Performance AnalysisApplication Performance Analysis

www.wildpackets.com 2008 WildPackets, Inc.

ay o e oay o e o

Director of Product ManagementDirector of Product Management

Apdex Symposium, Las Vegas

CMG Session 338

The Need

Service Level Agreements stipulate consistent

ualit of Service Uptime

Performance

Availability of specific applications

IT services must support business objectives

Difficult to quantify user satisfaction and efficiency

2008 WildPackets, Inc. 2CMG Apdex Track -WildPackets

Response time or network utilization numbers are notenough


2/8

Solution: Let Apdex Guide The Way

Apdex A numerical measure ofuser satisfaction with the

performance of enterprise applications Reduces many measurements into a single number Uniform 0-1 scale, 0 = no users satisfied, 1 = all users

satisfied Comparable metric across all applications Based on a specification produced by an alliance of vendors

(www.apdex.org)


ac e s xper ys ems Built-in intelligence for network application events

Packet Visualizer Conversation-oriented analysis and graphs "What If" view, and other configurable monitors/ thresholds

Apdex:Always Pointing North



3/8

Is It the Network or the Application?

Apdex is your compass

Indicating the magnitude of the problem

Preliminary analysis involves identifying primary events

Anything related to Slow

Depending on what events we see, we will know who is at fault

Secondary analysis includes application-specific and

network-specific events:


Application-specific Network-specific

- HTTP slow response time - T CP slow segment recovery

- Oracle slow response time - Slow retransmissions

- Inefficient client - Slow acknowledgements

- Low throughput

Let Experts do the analysis

Case Study: Apdex Reveals a Problem


ERP Application Server Performance has

fallen below the SLA only rated Fair


4/8


5/8

Follow Events to Seek the Root Cause


The Power ofSelect RelatedRight-click on any highlighted packet and do a Select

Related, then By Flow



6/8

Getting to the Root Cause

When we select the

ow erver

Response Time

event, two sessions

to the same server

are highlighted.

This looks to be a

s stem or


application issue

not the network.

But we need proof!

Visual Expert is the Proof!Two requests for data, two quick TCP Acks, but then a long delay

before the server sends the requested data

Payload

Length = 0

Payload

Requests andAcks

Then the Data

gets returned

much later


Length =1260


7/8

A Closer Look

Looking more granular at the timing, we see that the ACK cameback in 70ms, but the data didnt get sent back for another 854ms!

Ack fast = Network

fast


Data slow =System slow

Tune the Expert for your network

Make these times relevant

for your network or the

as a an



8/8

Documents

Session338.2Botelho