In a Windows system, the desktop heap is a memory area which is used whenever a process is activated.
Regardless of Systemwalker Operation Manager usage, the desktop heap may run out if a large number of processes are activated.
When using Systemwalker Operation Manager, you should pay attention to the desktop heap in the following cases:
Operating multiple subsystems
The number of Systemwalker Operation Manager service processes increases according to the number of subsystems, causing more of the desktop heap to be used.
Executing many jobs at a time
As the desktop heap is consumed when executing jobs, the more jobs are executed, the more desktop heap is consumed.
If the desktop heap is exhausted when multiple jobs are running concurrently, jobs are abnormally terminated with exception code 0xC0000142 or 0x40000999.
A value from 1 to 999 can be set for Max Execution Jobs. For a stable system operation, it is recommended to set this value within 30.
Compressing a large number of files at a time by using the File Compression/Expansion Command (fprssvr/fprscli)
When compressing multiple files, the more files are compressed, the more desktop heap is consumed because much temporary memory is used for compression processing.
If the desktop heap is exhausted while compressing multiple files, the following messages are displayed and the file compressions by file compression/expansion (fprssvr/fprscli) commands are failed.
For fprssvr:
0x2997(0x8): The heap for creating file table is not enough. |
For fprscli:
0xa997(0x8): The heap for creating file table is not enough. |
It is recommended to control the number of files to be compressed at a time within 500. To compress more files, divide compression work into multiple times.
