Sizing guidelines for the OpenEdge Management Trend Database
As OpenEdge Management runs, it gathers statistics on defined resources. These statistics are accumulated in several tables in the OpenEdge Management Trend Database. Every time OpenEdge Management trends data from a resource, a sample is added to that particular table. The following example shows how the amount of data trended affects the size of the OpenEdge Management Trend Database.
Example
For this example, the following quantities of trends are used for one trend sample:
The following are single rows in the OpenEdge Management Trend Database:
Note: If Table Statistics and Index Statistics are trended, there are 50 rows of each.The sample resources will render approximately 12.2K worth of data stored in the OpenEdge Management Trend Database. This data is broken down as follows:
If Table Statistics and Index Statistics are trended, they result in 5.4K and 7.1K worth of data, respectively. Additional index information for Table and Index Statistics rows results in approximately 920 bytes.
Scenario one
Using the quantities and values defined for the example, trending every 5 minutes for 24 hours over a 7-day period results in 2016 samples (288 5-minute periods in a day multiplied by 7 days). These 2016 samples result in an OpenEdge Management Trend Database of approximately 28.3MB.
Scenario two
Using the quantities and values defined for the example, trending every 15 minutes for 24 hours over a 7-day period results in 672 samples (96 15-minute periods in a day multiplied by 7 days). These 672 samples result in an OpenEdge Management Trend Database of approximately 22.5MB.
Copyright © 2008 Progress Software Corporation www.progress.com Voice: (781) 280-4000 Fax: (781) 280-4095 |