Job Management Partner 1/Performance Management - Agent Option for Enterprise Applications Description, User's Guide and Reference
The memory requirements vary depending on the setup conditions and on the conditions under which PFM - Agent for Enterprise Applications will be used.
- Organization of this subsection
- (1) Memory requirements for the entire system
- (2) Memory requirements during command execution
(1) Memory requirements for the entire system
The following table provides general estimates of the memory requirements of PFM - Agent for Enterprise Applications. The initial status refers to the state in which one instance of PFM - Agent for Enterprise Applications is run.
Table A-1 Memory requirements
Status of PFM - Agent for Enterprise Applications Required memory size (MB) Windows Server 2003 Windows Server 2008 HP-UX Solaris AIX Operation in initial status 37 44 70 60 40 Operation in other than initial status (37 + a + b) x number-of-instances (44 + a + b) x number-of-instances (70 + a + b) x number-of-instances (60 + a + b) x number-of-instances (40 + a + b) x number-of-instances
- Legend:
- a: Amount of memory space required by the jr3alget command when the CCMS Alert Monitor Command (PD_ALMX) record is collected. For details about the memory requirements for commands, see A.1(2) Memory requirements during command execution.
- b: Amount of memory space required by the jr3slget command when the System Log Monitor Command (PD_SLMX) record is collected. For details about the memory requirements for commands, see A.1(2) Memory requirements during command execution.
(2) Memory requirements during command execution
The following table shows the formulas for estimating memory requirements when the commands provided by PFM - Agent for Enterprise Applications are executed.
Table A-2 Memory requirements during command execution
Command Required memory size per command execution (MB) Windows Server 2003 Windows Server 2008 HP-UX Solaris AIX jr3alget 15 + 0.005 x a 17 + 0.005 x a 12 + 0.006 x a 16 + 0.005 x a 8 + 0.006 x a jr3slget 13 + 0.001 x b 15 + 0.001 x b 12 + 0.002 x b 16 + 0.001 x b 8 + 0.001 x b
- Legend:
- a: Total number of CCMS alerts that have occurred at the target monitor
- b: Total number of system logs that have occurred within the extraction period
- The extraction period depends on whether the -lasttime option is specified:
When the -lasttime option is specified: Time elapsed since the time of the previous execution of the command
When the -lasttime option is omitted: Time elapsed since 00:00:00 on the date of command execution
All Rights Reserved. Copyright (C) 2010, Hitachi, Ltd.