MethodCacheLimit

Integer (prefix multiplier)

5M for 64‑bit nodes; 512K for 32‑bit nodes

Purpose

The MethodCacheLimit parameter specifies the maximum amount of memory that is allocated for an interpreter method cache.

The optimum value for this parameter varies, depending on the:

Amount of physical memory available on your workstation.
Average size of methods and the number that are executing at one time; that is, being called by another method.

The minimum value is 64K bytes.

When a single cache for all processes within a node is used, this parameter takes effect when the node is initialized.

When multiple caches are used, the parameter takes effect when a process is initiated.

Hints

When a method is executed, the JADE interpreter must load the method code into the interpreter method cache for execution. The current copy is used if the method is not in use, it is already loaded in the cache, and it has not been modified. If a method is called frequently, tuning the cache size may result in substantial time-savings.

From version 2018.0.01, to determine method load counts and the amount by which the method cache limit is exceeded, refer to the method load times and cache overflow :

Sections in your profile report. For details about reporting profile information and tracing methods in runtime applications, see "Reporting Profile Statistics" under "Profiling an Application", in Chapter 1 of the JADE Runtime Application Guide.
Rows in the Method Cache Statistics table in the Process Information view of the JADE Monitor. For details, see "Displaying Process Method Cache Statistics" under "Performing Popup Menu Command Actions", in Chapter 2 of the JADE Monitor User's Guide.
Values in the notification userInfo output when calling the Process class sendMethodCacheStatistics method.

From version 2018.0.01, the MethodCacheLifetime parameter, which defaults to zero (0) for 32‑bit nodes and to 600000 milliseconds (that is, 10 minutes) for 64‑bit nodes, specifies the number of milliseconds a method must be in cache before it is made available for removal.

If you specify a MethodCache parameter value of Multiple when you are running in JADE thin client mode, up to the maximum amount of memory that you allocate by using the MethodCacheLimit parameter may be allocated for each end user. When you set cache parameters and you have a lot of JADE nodes, you need to consider the resource that is available on the machine as a whole.