135 lines
9.1 KiB
HTML
135 lines
9.1 KiB
HTML
<?xml version="1.0" encoding="UTF-8"?>
|
|
<!DOCTYPE html
|
|
PUBLIC "-//W3C//DTD XHTML 1.0 Transitional//EN" "http://www.w3.org/TR/xhtml1/DTD/xhtml1-transitional.dtd">
|
|
<html lang="en-us" xml:lang="en-us">
|
|
<head>
|
|
<meta http-equiv="Content-Type" content="text/html; charset=utf-8" />
|
|
<meta name="security" content="public" />
|
|
<meta name="Robots" content="index,follow" />
|
|
<meta http-equiv="PICS-Label" content='(PICS-1.1 "http://www.icra.org/ratingsv02.html" l gen true r (cz 1 lz 1 nz 1 oz 1 vz 1) "http://www.rsac.org/ratingsv01.html" l gen true r (n 0 s 0 v 0 l 0) "http://www.classify.org/safesurf/" l gen true r (SS~~000 1))' />
|
|
<meta name="DC.Type" content="concept" />
|
|
<meta name="DC.Title" content="Understanding disk consumption by Collection Services" />
|
|
<meta name="abstract" content="The amount of disk resource Collection Services consumes varies greatly depending on the settings that you use." />
|
|
<meta name="description" content="The amount of disk resource Collection Services consumes varies greatly depending on the settings that you use." />
|
|
<meta name="DC.Relation" scheme="URI" content="rzahxcollectdatacs.htm" />
|
|
<meta name="copyright" content="(C) Copyright IBM Corporation 1998, 2006" />
|
|
<meta name="DC.Rights.Owner" content="(C) Copyright IBM Corporation 1998, 2006" />
|
|
<meta name="DC.Format" content="XHTML" />
|
|
<meta name="DC.Identifier" content="rzahxcollservdisk" />
|
|
<meta name="DC.Language" content="en-us" />
|
|
<!-- All rights reserved. Licensed Materials Property of IBM -->
|
|
<!-- US Government Users Restricted Rights -->
|
|
<!-- Use, duplication or disclosure restricted by -->
|
|
<!-- GSA ADP Schedule Contract with IBM Corp. -->
|
|
<link rel="stylesheet" type="text/css" href="./ibmdita.css" />
|
|
<link rel="stylesheet" type="text/css" href="./ic.css" />
|
|
<title>Understanding disk consumption by Collection Services</title>
|
|
</head>
|
|
<body id="rzahxcollservdisk"><a name="rzahxcollservdisk"><!-- --></a>
|
|
<!-- Java sync-link --><script language="Javascript" src="../rzahg/synch.js" type="text/javascript"></script>
|
|
<h1 class="topictitle1">Understanding disk consumption by Collection Services</h1>
|
|
<div><p>The amount of disk resource Collection Services consumes varies greatly depending on the settings that you use.</p>
|
|
<p>For illustration purposes, assume that Collection Services is used daily and cycles at midnight, causing each *MGTCOL object to contain one day's worth of data collection. Next, establish a base size
|
|
for one day's worth of data collection by using the default properties for Collection Services. A standard plus protocol profile with an interval value of 15 minutes can collect 500 MB of data in a *MGTCOL
|
|
object. The size actually collected per day using the default properties can vary greatly depending on system size and usage. The 500 MB example might represent a higher-end system that is heavily used.</p>
|
|
|
|
<div class="tablenoborder"><table cellpadding="4" cellspacing="0" summary="" frame="border" border="1" rules="all"><thead align="left"><tr><th valign="top" id="d0e22">Interval rate</th>
|
|
<th valign="top" id="d0e24">Intervals per collection</th>
|
|
<th valign="top" id="d0e26">Multiplier</th>
|
|
<th valign="top" id="d0e28">Size in MB</th>
|
|
</tr>
|
|
</thead>
|
|
<tbody><tr><td valign="top" headers="d0e22 ">15 minutes</td>
|
|
<td valign="top" headers="d0e24 ">96</td>
|
|
<td valign="top" headers="d0e26 ">1</td>
|
|
<td valign="top" headers="d0e28 ">500</td>
|
|
</tr>
|
|
</tbody>
|
|
</table>
|
|
</div>
|
|
<p>The size of one day's worth of data is directly proportional to the number of intervals collected per collection period. For example, changing the interval rate from 15 minutes to 5 minutes increases
|
|
the number of intervals by a factor of 3 and increases the size by the same factor.</p>
|
|
|
|
<div class="tablenoborder"><table cellpadding="4" cellspacing="0" summary="" frame="border" border="1" rules="all"><thead align="left"><tr><th valign="top" id="d0e50">Interval rate</th>
|
|
<th valign="top" id="d0e52">Intervals per collection</th>
|
|
<th valign="top" id="d0e54">Multiplier</th>
|
|
<th valign="top" id="d0e56">Size in MB</th>
|
|
</tr>
|
|
</thead>
|
|
<tbody><tr><td valign="top" headers="d0e50 ">15 minutes</td>
|
|
<td valign="top" headers="d0e52 ">96</td>
|
|
<td valign="top" headers="d0e54 ">1</td>
|
|
<td valign="top" headers="d0e56 ">500</td>
|
|
</tr>
|
|
<tr><td valign="top" headers="d0e50 ">5 minutes</td>
|
|
<td valign="top" headers="d0e52 ">288</td>
|
|
<td valign="top" headers="d0e54 ">3</td>
|
|
<td valign="top" headers="d0e56 ">1500</td>
|
|
</tr>
|
|
</tbody>
|
|
</table>
|
|
</div>
|
|
<p>To continue this example, the following table shows the size of one *MGTCOL object produced each day by Collection Services at each interval rate, using the default standard plus protocol profile.</p>
|
|
|
|
<div class="tablenoborder"><table cellpadding="4" cellspacing="0" summary="" frame="border" border="1" rules="all"><thead align="left"><tr><th valign="top" id="d0e87">Interval rate</th>
|
|
<th valign="top" id="d0e89">Intervals per collection</th>
|
|
<th valign="top" id="d0e91">Multiplier</th>
|
|
<th valign="top" id="d0e93">Size in MB</th>
|
|
</tr>
|
|
</thead>
|
|
<tbody><tr><td valign="top" headers="d0e87 ">15 minutes</td>
|
|
<td valign="top" headers="d0e89 ">96</td>
|
|
<td valign="top" headers="d0e91 ">1</td>
|
|
<td valign="top" headers="d0e93 ">500</td>
|
|
</tr>
|
|
<tr><td valign="top" headers="d0e87 ">5 minutes</td>
|
|
<td valign="top" headers="d0e89 ">288</td>
|
|
<td valign="top" headers="d0e91 ">3</td>
|
|
<td valign="top" headers="d0e93 ">1500</td>
|
|
</tr>
|
|
<tr><td valign="top" headers="d0e87 ">1 minutes</td>
|
|
<td valign="top" headers="d0e89 ">1440</td>
|
|
<td valign="top" headers="d0e91 ">15</td>
|
|
<td valign="top" headers="d0e93 ">7500</td>
|
|
</tr>
|
|
<tr><td valign="top" headers="d0e87 ">30 seconds</td>
|
|
<td valign="top" headers="d0e89 ">2880</td>
|
|
<td valign="top" headers="d0e91 ">30</td>
|
|
<td valign="top" headers="d0e93 ">15000</td>
|
|
</tr>
|
|
<tr><td valign="top" headers="d0e87 ">15 Seconds</td>
|
|
<td valign="top" headers="d0e89 ">5760</td>
|
|
<td valign="top" headers="d0e91 ">60</td>
|
|
<td valign="top" headers="d0e93 ">30000</td>
|
|
</tr>
|
|
</tbody>
|
|
</table>
|
|
</div>
|
|
<p>The size of a *MGTCOL object, in this example, can vary from 500 MB to 30 GB depending on the rate of collection. You can predict a specific system's disk consumption for one day's collection interval
|
|
through actual observation of the size of the *MGTCOL objects created, using the default collection interval of 15 minutes and the standard plus protocol profile as the base and then using the multiplier
|
|
from the above table to determine the disk consumption at other collection intervals. For example, if observation of the *MGTCOL object size reveals that the size of the object for a day's collection is
|
|
50 MB for 15-minute intervals, then you could expect Collection Services to produce *MGTCOL objects with a size of 3 GB when collecting data at 15-second intervals.</p>
|
|
<div class="note"><span class="notetitle">Note:</span> Use caution when considering a collection interval as frequent as 15 seconds. Frequent collection intervals can adversely impact system performance.</div>
|
|
<div class="section"><h4 class="sectiontitle">Retention period</h4><p>The retention period also plays a significant role in the amount of disk resource that Collection Services consumes. The default retention period is one day. However,
|
|
practically speaking, given the default values, a *MGTCOL object is deleted on the third day of collection past the day on which it was created. Thus, on the third day of collection there is two days' worth
|
|
of previously collected data plus the current day's data on the system. Using the table above, this translates into having between 1 GB and 1.5 GB of disk consumption at 15-minute intervals, and 60 to 90
|
|
GB of disk consumption at 15-second intervals on the system during the third day and beyond.</p>
|
|
<p>The formula to calculate disk consumption based on the retention period value is:</p>
|
|
<pre>(Retention period in days + 2.5) * Size of one day's collection =
|
|
Total Disk Consumption</pre>
|
|
<div class="note"><span class="notetitle">Note:</span> 2.5 corresponds to two days of previous collection data, and an average of the current day (2 days + 1/2 day).</div>
|
|
<p>Using the above tables and formula, a retention period of 2 weeks
|
|
gives you a disk consumption of 8.25 GB at 15-minute intervals and 495 GB at 15-second intervals for the example system.</p>
|
|
<p>It is important to understand the disk consumption by Collection Services to
|
|
know the acceptable collection interval and retention period for a given system. Knowing this can ensure that disk consumption will not cause system problems. Remember to consider that a system monitor
|
|
or a job monitor can override a category's collection interval to graph data for a monitor. A system administrator must ensure that monitors do not inadvertently collect data at intervals that will cause
|
|
excess data consumption.</p>
|
|
</div>
|
|
</div>
|
|
<div>
|
|
<div class="familylinks">
|
|
<div class="parentlink"><strong>Parent topic:</strong> <a href="rzahxcollectdatacs.htm" title="Use Collection Services to collect performance data for later analysis by the Performance Tools for iSeries licensed program or other performance report applications, iSeries Navigator monitors, and the graph history function. (If you prefer viewing real-time performance data, system monitors provide an easy-to-use graphical interface for monitoring system performance.)">Collection Services</a></div>
|
|
</div>
|
|
</div>
|
|
</body>
|
|
</html> |