measure and monitor before you change anything

Here is something to think about...
If you are going to do a major change to a machine/application then it is worthwhile investing some time in getting some baseline measurements of the system's configuration/performance before you change anything. Exactly what is worth gathering depends on the machine but I see many escalations where we are forced to explain why after a major change the system appears to be slow but with no possibility to gather any data from before the changes.

The explorer scripts do a good job of capturing the base solaris/machine configuration but you also need to capture the configuration of the primary application. You then need to gather performance data from Solaris and the application.

An example of this is a customer moving to 64 bit oracle who suffers much slower i/o performance, luckily there are some snippets of sar data from before the change that allowed us to spot that the amount of i/o had greatly increased due to changes in the Oracle configuration

prepare for the worst and it won't happen.

Comments:

Ahhh, you ended up with that escalation.

As someone who works performance calls I can't agree more strongly with what Tim says here.

If we don't have baselines to compare against, it gets really hard to troubleshoot this kind of call.

Alan.

Posted by Alan Hargreaves on September 09, 2005 at 06:31 PM GMT+00:00 #

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

timatworkhomeandinbetween

Search

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
News

No bookmarks in folder

Blogroll

No bookmarks in folder