| Physical memory (HTnM-Agent for RAID (When Hybrid Store is adopted)) | |||||||||||||||||||||||||||||||
| return to main contents page | |||||||||||||||||||||||||||||||
| return to "Management server" contents page | |||||||||||||||||||||||||||||||
| Note | |||||||||||||||||||||||||||||||
| The memory described here is the "virtual memory", which is the combination of the actual memory (the physical memory capacity that is actually required for each product) and the temporary area on the hard disk (the paging files | |||||||||||||||||||||||||||||||
| or the swap files that are actually required for each product). If enough actual memory cannot be secured, the processing performance might be affected. | |||||||||||||||||||||||||||||||
| Agent for RAID |
|||||||||||||||||||||||||||||||
| Table 1 Agent for RAID
memory requirements provides general estimates of the amount of memory
required for Agent for RAID. The term, initial conditions, refers to running
one instance of Agent for RAID. |
|||||||||||||||||||||||||||||||
| Table 1 Agent for RAID memory requirements | |||||||||||||||||||||||||||||||
| Status of
Agent for RAID |
Memory requirements (megabytes) | ||||||||||||||||||||||||||||||
| Windows | Linux | ||||||||||||||||||||||||||||||
| At installation | a+b+c+d+e+f | a+b+c+d+e+f | |||||||||||||||||||||||||||||
| Operating
under initial conditions |
(a1+b1+c1+f1) + (a2+b2+c2+f2) + ... + (an+bn+cn+fn)+d+e |
(a1+b1+c1+f1) + (a2+b2+c2+f2) + ... + (an+bn+cn+fn)+d+e |
|||||||||||||||||||||||||||||
| a: Memory requirement
for the jpcagtd process (When the number of instances is n, the memory
requirement for each instance varies from a1 to an.) |
|||||||||||||||||||||||||||||||
| b: Memory requirement
for the jpcsto process (When the number of instances is n, the memory
requirement for each instance varies from b1 to bn) |
|||||||||||||||||||||||||||||||
| c: Memory requirement
for the hpmrlcollector process (When the number of instances is n, the memory
requirement for each instance varies from c1 to cn) (see Note 1) |
|||||||||||||||||||||||||||||||
| d: Amount of memory
required by Tuning Manager - Agent REST Web Service required when the Tuning
Manager API is enabled: (see Note 2) |
|||||||||||||||||||||||||||||||
| Windows: 1,024 MB | |||||||||||||||||||||||||||||||
| Linux: 1,024 MB | |||||||||||||||||||||||||||||||
| e: Amount of memory required by Tuning Manager - Agent REST Application Service. For details on estimating the amount of required memory, see "Memory required for Tuning Manager - Agent REST Application Service". | |||||||||||||||||||||||||||||||
| f: For the amount of memory required for the performance data collection process using TCP/IP, see "Memory requirements for the TCP/IP-based data collection process". In the above expressions, f1 to fn indicate the memory requirements for the instances of a process when the number of instances is n. | |||||||||||||||||||||||||||||||
| n: Number of instances of the agent | |||||||||||||||||||||||||||||||
| Note 1: You must estimate the memory requirement for this process only when collecting configuration information of the storage system at the timing defined in the collection time definition file (conf_refresh_times.ini). | |||||||||||||||||||||||||||||||
| Note 2: This memory size required by Tuning Manager - Agent REST Web Service will be shared by all Agents that are operated by using Hybrid Store and installed on the same host. Thus, when calculating the memory size requirement, | |||||||||||||||||||||||||||||||
| add this memory size required by Tuning Manager - Agent REST Web Service for only one Agent. | |||||||||||||||||||||||||||||||
| The memory requirements for the jpcagtd, jpcsto, and hpmrlcollector processes vary depending on the OS and the storage system monitored by each instance. | |||||||||||||||||||||||||||||||
| Table 2 Memory requirements for the jpcagtd process, Table 3 Memory requirements for the jpcsto process, and Table 4 Memory requirements for the hpmrlcollector process show the memory requirements for each process. | |||||||||||||||||||||||||||||||
| Table 2 Memory requirements for the jpcagtd process | |||||||||||||||||||||||||||||||
| Monitored storage system | Memory requirements (megabytes) | ||||||||||||||||||||||||||||||
| Windows | Linux | ||||||||||||||||||||||||||||||
| Hitachi AMS2000/AMS/WMS/SMS series | 200 | 350 | |||||||||||||||||||||||||||||
| HUS100 series | 200 | 350 | |||||||||||||||||||||||||||||
| Universal Storage Platform V/VM series | 870 | 1600 | |||||||||||||||||||||||||||||
| Virtual Storage Platform | 1220 | 2000 | |||||||||||||||||||||||||||||
| HUS VM | 870 | 1600 | |||||||||||||||||||||||||||||
| VSP G1000, G1500, VSP F1500 | 1220 | 2000 | |||||||||||||||||||||||||||||
| VSP Gx00 models or VSP Fx00 models | 870 | 1600 | |||||||||||||||||||||||||||||
| Table 3 Memory requirements for the jpcsto process | |||||||||||||||||||||||||||||||
| Monitored storage system | Memory requirements (megabytes) | ||||||||||||||||||||||||||||||
| Windows | Linux | ||||||||||||||||||||||||||||||
| Hitachi AMS2000/AMS/WMS/SMS series | 30 | 150 | |||||||||||||||||||||||||||||
| HUS100 series | 30 | 150 | |||||||||||||||||||||||||||||
| Universal Storage Platform V/VM series | 200 | 300 | |||||||||||||||||||||||||||||
| Virtual Storage Platform | 200 | 300 | |||||||||||||||||||||||||||||
| HUS VM | 120 | 200 | |||||||||||||||||||||||||||||
| VSP G1000, G1500, VSP F1500 | 200 | 300 | |||||||||||||||||||||||||||||
| VSP Gx00 models or VSP Fx00 models | 120 | 200 | |||||||||||||||||||||||||||||
| Table 4 Memory requirements for the hpmrlcollector process | |||||||||||||||||||||||||||||||
| Monitored storage system | Memory requirements (megabytes) | ||||||||||||||||||||||||||||||
| Windows | Linux | ||||||||||||||||||||||||||||||
| Hitachi AMS2000/AMS/WMS/SMS series | 120 | 180 | |||||||||||||||||||||||||||||
| HUS100 series | 120 | 180 | |||||||||||||||||||||||||||||
| Universal Storage Platform V/VM series | 290 | 600 | |||||||||||||||||||||||||||||
| Virtual Storage Platform | 660 | 1100 | |||||||||||||||||||||||||||||
| HUS VM | 220 | 450 | |||||||||||||||||||||||||||||
| VSP G1000, G1500, VSP F1500 | 660 | 1100 | |||||||||||||||||||||||||||||
| VSP Gx00 models or VSP Fx00 models | 220 | 450 | |||||||||||||||||||||||||||||
| Memory required for Tuning Manager - Agent REST Application Service | |||||||||||||||||||||||||||||||
| The formula for estimating the memory required for Tuning Manager - Agent REST Application Service is as follows: | |||||||||||||||||||||||||||||||
| A = 600 + 175 x B/1,000+C | |||||||||||||||||||||||||||||||
| A: Maximum amount of memory required (in megabytes) | |||||||||||||||||||||||||||||||
| B: Total number of LDEVs to be monitored for all the instances that are managed by the applicable Tuning Manager - Agent REST Application Service | |||||||||||||||||||||||||||||||
| C: Amount of memory required for the Alert Function. For details, see "Memory requirements for the Alert Function". | |||||||||||||||||||||||||||||||
| Example (when the number of LDEVs is 8,000): | |||||||||||||||||||||||||||||||
| A = 600 + 175 x 8,000/1,000 = 2,000 (in megabytes) | |||||||||||||||||||||||||||||||
| Note that, at the time of installation, you can select the maximum amount of required memory to be used by Tuning Manager - Agent REST Application Service from the following three sizes: | |||||||||||||||||||||||||||||||
| 2GB | |||||||||||||||||||||||||||||||
| 4GB | |||||||||||||||||||||||||||||||
| 6GB | |||||||||||||||||||||||||||||||
| You can change the maximum memory size by following the steps in the chapter of changing the maximum memory size used for Hybrid Store in the Tuning Manager Agent Administration Guide. | |||||||||||||||||||||||||||||||
| Note: If the required memory capacity that you calculated exceeds 6 GB, select 6 GB as the maximum memory size when you install Agent for RAID. | |||||||||||||||||||||||||||||||
| After Agent for RAID is installed, change the maximum memory size to the required memory capacity that you calculated. | |||||||||||||||||||||||||||||||
| Memory requirements for the TCP/IP-based data collection process | |||||||||||||||||||||||||||||||
| The amount of memory required for the performance data collection process using TCP/IP is determined based on the memory size that the user specified in the jpcinssetup command when creating an instance. The following shows the expression for estimating the memory size to be specified in the jpcinssetup command. | |||||||||||||||||||||||||||||||
| For details on how to set memory by using the jpcinssetup command, see Updating an instance environment in the Tuning Manager Installation Guide. | |||||||||||||||||||||||||||||||
| A = 100 + B | |||||||||||||||||||||||||||||||
| B is the largest of the values obtained from the expressions in the Memory requirements column of the following table. | |||||||||||||||||||||||||||||||
| Table 5 Memory requirements for each record to be collected | |||||||||||||||||||||||||||||||
| Record to be collected | Memory
requirements (megabytes) |
||||||||||||||||||||||||||||||
| PI_LDSX PI_LDUR PI_LDTC PI_ELDS |
0.04 * number of LDEVs / sampling interval (min.) | ||||||||||||||||||||||||||||||
| PI_LSP | 0.07 * number of LU Paths / sampling interval (min.) | ||||||||||||||||||||||||||||||
| PI_LDU PI_LUSP PI_LTSP |
0.05 * number of LU Paths / sampling interval (min.) | ||||||||||||||||||||||||||||||
| For example, to collect the PI_LDSX, PI_LDUR, and PI_LDU records at a sampling interval of 1 minute when 8,000 LDEVs and 10,000 LU Paths exist, the required memory size is as follows: | |||||||||||||||||||||||||||||||
| PI_LDSX or PI_LDUR = 0.04 * 8,000 / 1 = 320 | |||||||||||||||||||||||||||||||
| PI_LDU = 0.05 * 10,000 / 1 = 500 | |||||||||||||||||||||||||||||||
| A=100+500=600 (megabytes) | |||||||||||||||||||||||||||||||
| Memory requirements for the Alert Function | |||||||||||||||||||||||||||||||
| The amount of memory required for the Alert Function differs depending on the number of conditional expressions (trigger type) for an agent host and the character length in the email text (the length of characters specified in the body variable of the email object) that is to be sent. | |||||||||||||||||||||||||||||||
| The following shows the amount of memory required for each of the given ranges of the total number of conditional expressions (trigger type) per agent host: | |||||||||||||||||||||||||||||||
| Table 6 Amount of memory required for the Alert Function (if the string length of the email body is 500 bytes or more): | |||||||||||||||||||||||||||||||
| OS | Total number of conditional expressions (trigger type) per agent host | Required memory size (MB) | |||||||||||||||||||||||||||||
| If occurrence frequency is used | If occurrence frequency is not used | ||||||||||||||||||||||||||||||
| All 64-bit OSs | 0 | 0 | 0 | ||||||||||||||||||||||||||||
| 1 - 200 | 1024 | 300 | |||||||||||||||||||||||||||||
| 201 - 2000 | 1536 | 800 | |||||||||||||||||||||||||||||
| 2001 - 10000 | 3584 | 3072 | |||||||||||||||||||||||||||||
| For each increment of 10,000, the value on the right is also required. | +2560 | +2560 | |||||||||||||||||||||||||||||
| Table 7 Amount of memory required for the Alert Function (if the string length of the email body is less than 500 bytes): | |||||||||||||||||||||||||||||||
| OS | Total number of conditional expressions (trigger type) per agent host | Required memory size (MB) | |||||||||||||||||||||||||||||
| If occurrence frequency is used | If occurrence frequency is not used | ||||||||||||||||||||||||||||||
| All 64-bit OSs | 0 | 0 | 0 | ||||||||||||||||||||||||||||
| 1 - 200 | 1024 | 300 | |||||||||||||||||||||||||||||
| 201 - 2000 | 1536 | 800 | |||||||||||||||||||||||||||||
| 2001 - 10000 | 2526 | 2048 | |||||||||||||||||||||||||||||
| For each increment of 10,000, the value on the right is also required. | +1536 | +1536 | |||||||||||||||||||||||||||||