Swat Analyze function and Java heap problems, continued

If you read my earlier blog about java heap problems with Analyze, here is an other change that you can make, but it has some risks.

Swat Analyze by default keeps the last 180 seconds worth of i/o detail in memory. This is done so that Swat can identify any i/o that takes up to 180 seconds (180 sounds high, but I have seen them). If you know for sure that you do not have any i/o taking longer than for instance 30 seconds, you can change this 180 second value.

When using the GUI, select the 'Settings' tab, click on the 'batch_prm' line, add '-a30' (don't add the quotes), click 'Save', and restart Analyze.

If you can't use the GUI, go to file 'options.sUSERID.ini' and manually change the value after 'batch_prm' to '-a30' and restart Analyze. 

Note though that then any i/o lasting longer than 30 seconds will NOT be recognized by Swat.

Comments:

Post a Comment:
  • HTML Syntax: NOT allowed
About

Blog for Henk Vandenbergh, author of Vdbench, and Sun StorageTek Workload Analysis Tool (Swat). This blog is used to keep you up to date about anything revolving around Swat and Vdbench.

Search

Categories
Archives
« April 2014
SunMonTueWedThuFriSat
  
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