4.4 Memory Allocation
When establishing new input data (or when working with data in general) it is important to consider memory. Recall that every time an object is created, memory is used. To avoid running out of space, you must allocate memory to each area.
Memory Management
CHPS runs on a Java platform and uses a Java script called "garbage collector" to free up memory.
The two types of memory in the system are Heap and PermGen (where the system stores metadata). This course deals with Heap.
Heap is where all objects get their memory.
As System Manager, you must configure the CHPS system to avoid memory loss. The default for Heap is 64 MB. Use caution when changing the default value. If Heap is too big, there could be a memory leak. If it is too small, the system might rob other areas of memory to operate. Memory allocation can be configured on the FSSs, MC, and OC.
Typical Memory Settings
| Server | Processes | Allocation |
|---|---|---|
| MC | FSListener, OCListener, Synchronization | 512 MB |
| MC | Task Manager, RemoteProxy, SystemMonitor | 64 - 128 MB |
| FSS | MCProxy | 64 MB |
| FSS | FewsShell | 512 -1024 MB |
The memory value for the Operator Client is highly variable, based on RFC. Ask other RFCs what setting works best for them and use that as a guideline.
Note: If OCListener/FSListener or FSS requires more than 1024 MB, look for unnecessary large files before increasing memory size.
For instructions on changing memory settings or optimizing the OC and FSS through memory allocation, refer to the job sheet.
Job Sheet: Checking/Changing Memory Settings