Estimating Space Requirements for Event Data

This section discusses two formulas that are used for estimating event data space requirements (in kilobytes).

  • Standard formula: Use the standard formula if the application server domain configuration is based on PeopleSoft-delivered small, medium, or large template.

  • Customized formula: Use the customized formula if the configuration is different from the templates.

This table describes the variables that are used in the formulas.

Notation Description Performance Monitor Default Value Navigation

A

Performance Monitor agent event sampling rate.

300 seconds

PeopleTools, and then Performance Monitor, and then Administration, and then Monitored Systems

N

Number of PeopleSoft systems that are monitored by Performance Monitor. This is the number of PeopleSoft databases appearing on the System Definitions search page.

NA

PeopleTools, and then Performance Monitor, and then Administration, and then Monitored Systems

D

Performance history retention period in days. This is the value that is set for the After N days option.

NA

PeopleTools, and then Performance Monitor, and then Administration, and then Monitored Systems

W

Number of web server domains for a monitored system. This is the total number of web servers appearing on the System Performance page.

NA

PeopleTools, and then Performance Monitor, and then System Monitor, and then System Performance

P

Number of application server domains for a monitored system. This is the total number of application servers appearing on the System Performance page.

NA

PeopleTools, and then Performance Monitor, and then System Monitor, and then System Performance

App

Number of server processes running in an application server domain for a monitored system. This is the number of program names appearing on for Server Status.

Use the following number per domain template that you choose:

  • Large = 60

  • Medium = 40

  • Small = 20

PSADMIN, and then Application Server, and then Administer a domain, and then Domain, and then Domain status menu, and then Server status

S

Number of monitored PeopleSoft Process Scheduler domains for a monitored system. This is the total number of Process Scheduler domains appearing on the System Performance page.

NA

PeopleTools, and then Performance Monitor, and then System Monitor, and then System Performance

Prcs

Number of server processes running in a PeopleSoft Process Scheduler domain for a monitored system. This is the number of program names appearing for Server status.

8

Increase this number if more than three Application Engine processes are configured.

PSADMIN, and then Process Scheduler, and then Show Status of a Process Scheduler Server, and then Domain, and then Domain status menu, and then Server status

MPrcs

Number of Master Scheduler for a monitored system.

1

NA

E

Number of KB per event row in the table.

Refer to the value in the following table for the target database.

NA

The following table helps you to determine the appropriate value for E (Number of KB per event row in the table).

Parameter ANSI/Unicode Oracle Microsoft SQL Server DB2 Db2 for z/OS

E

ANSI

.4

.4

.5

.6

E

Unicode

.7

.7

.9

1.1

Using the Standard Formula

The formula that you use differs depending on the template used in the application server configuration.

Field or Control Description

Large

N x D x [8 x W + 180 x P + 16 x S + 1] x 86400 / A x E

Medium

N x D x [8 x W + 120 x P + 16 x S + 1] x 86400 / A x E

Small

N x D x [8 x W + 60 x P + 16 x S + 1] x 86400 / A x E

Using the Customized Formula

Use this formula if the application server configuration is different from the standard templates.

N x D x [8 x W + 3 x P x App + 2 x S x Prcs + MPrcs] x 86400 / A x E

Note:

Eight events are reported per web server domain. Two events are reported per web server (JVM status and network status), one event per web site, and five events per web site for PeopleSoft servlets (psp, psc, cs, *, and Scheduler Transfer).

If multiple systems are monitored and each is configured slightly differently, that is, the numbers of application server processes are different, then use the formula to estimate the requirement for each system separately.