apm performance day 2013 - improve your mean time to innocence

Post on 05-Dec-2014

1.114 Views

Category:

Technology

1 Downloads

Preview:

Click to see full reader

DESCRIPTION

When a new application is experiencing performance issues who gets the blame; is it the network, servers or application itself? See how using Compuware's APM Solution a customer validated the performance issue and was able to isolate and understand where the problem lay and what the true impact was, thereby stopping the blame game.

TRANSCRIPT

1 1

James Neal

2 2

The Situation

The Customer

Service Provider A

Service Provider B

Service Provider C

Application Network Hosting

3

So…how did we help?

4

Datacente

r

Define

XML/SOAP

SQL

http

Define the application landscape

5

Define the application landscape

http XML/SOAP

Net

wo

rk U

tilis

atio

n

Netw

ork Perfo

rman

ce

Site C

Site D

Site A

Site B

Key

6

Understand application performance

Datacenter

Database Application &

Middleware

Presentation

Tier

Router &

Load Balancer

7

Understand application performance

Order to Cash

Plan to Produce

Record to Report

80% Affected

Order to Cash

Plan to Produce

Record to Report

8.4s Current

2.5s Baseline

4.6k Fast Trans.

9.7k Slow Trans.

App. Tier

Server – ap213d01

8

Is there actually a problem…?

9

NewApp – Regional Performance

10

What does good actually look like…?

11

NewApp – Good Performance: EMEA Areas

12

NewApp – Good Performance: Switzerland Site

13

NewApp – Good Performance: Site Transactions

14

NewApp – Good Performance: Site “Get File” Transaction

15

NewApp – Good Performance: Site “Query” Transaction

16

How does bad performance compare…?

17

NewApp – Bad Performance: 3rd Party Areas

18

NewApp – Bad Performance: 3rd Party Transactions

19

NewApp – Bad Performance: 3rd Party “Get File” Transaction

20

NewApp – Bad Performance: 3rd Party “Query” Transaction

21

Who are these users and where are they…?

22

Affected Users

23 23

Within 10 minutes we were able to…

•Validate there was an issue

• Identify where that issue lay

•Understand who was affected

•Provide a plan for resolution

top related