www.sun.com/123

At a very high level performance analysis follows a cycle where we try to define the problem to be solved (shame it is often the part least attention is payed to), then run through a cycle of refining where time is being spent or identifying the resources are being used. Might also throw in a best practice review of the configuration.

I did some work with an Italian banking customer this morning. We used SharedShell taking about 10 minutes of analysis to establish root cause and maybe another 10 minutes for me to write up the root cause and solution. While SharedShell has been out for a few months, its the 1st time I had been invited to use it by a customer, rather than asking if it was a possibility. Being able to ask if the customer could see the performance issue they were concerned about at a particular moment in the chat window should not be underestimated in terms of removing misunderstanding and delay. The analysis would have required at least 2 steps beyond what a single GUDS run would give you, so a best case turn around time for an engineer running the same commands and emailing back the output or putting it on the SunSolve server for me to analyze is usually measured in hours. I guess we saved at least 3 hours on the time to resolution. For harder performance cases I would expect the time saving to be greater, but far more important to me is that the accuracy of diagnosis will be higher.

Well worth checking out and the effort in getting security clearance from your organisations prior to wanting to use it.

Comments:

Post a Comment:
Comments are closed for this entry.
About

clive

Search

Categories
Archives
« April 2014
MonTueWedThuFriSatSun
 
1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
20
21
22
23
24
25
26
27
28
29
30
    
       
Today