Standard Settings

The use of SICS functions obviously varies from user to user and from one SICS session to another. Likewise, the amount of data being processed varies from user to user and from one SICS session to another. Therefore, it is not possible to pre-set the heap memory size in such a way that,

1. the JVM never runs out of memory, and
2. there is no gross over-allocation of memory.

The best one can do, is to pre-set the memory limits such that

1. the JVM will not run out of memory for ’normal’ work
2. the over-allocation over memory is not too large.

Obviously, there is no fixed answer to what is ’normal’ and ’not too large’. If SICS requires more memory than available, the JVM will run out of memory and SICS will be terminated. At the same time the limit must be as low as possible, otherwise SICS will consume more memory than needed and thereby limit the resources available to other processes running on the same computer.

Based on experience, DXC delivers SICS with a set of recommended memory values. However, each SICS installation must make their own experience and judgment on this topic. It may be necessary to increase (or even decrease) memory limits for all or some users / user groups, or when working with certain functions.

For instance, running large batch jobs (typically large accounting orders) will most likely require substantially more heap memory because large amounts of data will be processed.
See Changing memory settings.

When installing SICS, there will be command files run_sics_workstation.bat and run_sics_sysadmin.bat to start the Workstation and the System Administration Utility, respectively. These files include JRE parameters that set, among other things, memory size values.

If you also installed the SICS Launcher, you will find the JRE command line parameters in the SICSJavaLauncher.ini file.

The maximum heap size is set with command line parameter -Xmx, for example -Xmx300m.

64-bit Memory Settings #

Table 1 - 64-bit Maximum Heap Size #