/sicsdocs/technical/misc/memory_settings/ Recent content in Memory settings on Hugo -- gohugo.io /sicsdocs/technical/misc/memory_settings/introduction/ Mon, 01 Jan 0001 00:00:00 +0000 /sicsdocs/technical/misc/memory_settings/introduction/ This document describes how you may change the memory settings of SICS. For most installations of SICS the standard settings are appropriate. Although the memory settings are carefully tailored to suite the memory usage of SICS, you may need to change them to fit a given SICS installation. Conditions that affect memory usage are data volumes, system settings and the functions and modules of SICS in use. /sicsdocs/technical/misc/memory_settings/background/ Mon, 01 Jan 0001 00:00:00 +0000 /sicsdocs/technical/misc/memory_settings/background/ SICS is programmed in Java. The SICS programs are compiled into so-called Java byte code format. The SICS Java byte codes are grouped into a number of compressed files called jars. These jars constitute the main part of a SICS installation. In order to run SICS, one must start a Java Virtual Machine (JVM), a computer program in its own right, and tell it where the Java byte code for SICS is stored, i. /sicsdocs/technical/misc/memory_settings/determine_java_version/ Mon, 01 Jan 0001 00:00:00 +0000 /sicsdocs/technical/misc/memory_settings/determine_java_version/ The Java version being used can be determined as follows: In Help->About SICS, go to System Info. Select the Java tab The properties java.version and java.runtime.version specifies the Java version. The property sun.arch.data.model specifies if the SICS is 64 or 32 bit. Note that this version of SICS requires 64-bit Java 17+. /sicsdocs/technical/misc/memory_settings/standard_settings/ Mon, 01 Jan 0001 00:00:00 +0000 /sicsdocs/technical/misc/memory_settings/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, the JVM never runs out of memory, and there is no gross over-allocation of memory. The best one can do, is to pre-set the memory limits such that /sicsdocs/technical/misc/memory_settings/identifying_memory_problems/ Mon, 01 Jan 0001 00:00:00 +0000 /sicsdocs/technical/misc/memory_settings/identifying_memory_problems/ If SICS terminates (abends) with an error message and one of the first lines of the walkback file is: ... java.lang.OutOfMemoryError: Java heap space ... then you have a heap memory problem. Examples of situations when such an error can occur are: Batch processing Long running task, e.g. accounting orders and periodic functions Reading large amounts of data from the SICS database, for instance, asking the Business Partner Ledger to return more than a few thousand balances. /sicsdocs/technical/misc/memory_settings/changing_memory_settings/ Mon, 01 Jan 0001 00:00:00 +0000 /sicsdocs/technical/misc/memory_settings/changing_memory_settings/ If you identified a memory problem as described in section 4, you may solve the problem by increasing the appropriate maximum memory size parameter. If you use the standard SICS setup, the Java command line parameters are located in the command files: run_sics_workstation.bat and run_sics_sysadmin.bat. Edit the relevant file and increase the -Xmx value. If you use the SICS Launcher setup the JRE command line parameters are located in the SICSJavaLauncher.