cancel
Showing results for 
Search instead for 
Did you mean: 

What is the default memory limit of Prognosis processes and can it be changed?

Moderator

What is the default memory limit of Prognosis processes and can it be changed?

What is the default memory limit of Prognosis processes and can it be changed?

 

1 ACCEPTED SOLUTION

Accepted Solutions
Highlighted
Moderator

Re: What is the default memory limit of Prognosis processes and can it be changed?

What is the default memory limit of Prognosis processes and can it be changed?

Prognosis processes have a self-imposed limit of memory usage of 200MB (note that this is the 'default' value built into the code, and is sometimes over-ridden by out-of-box SET MEM-SIZE settings in the PROGNOSIS configuration).

If a Prognosis process exceeds this default limit, then it will terminate, and log an error such as the following to the wvlog:

"EXTENDED MEMORY LIMIT EXCEEDED"

The default memory limit for any process can be set manually with an entry in the Prognosis configuration that looks like this:

SET MEM-SIZE ( <process name> , nnn )

where <process name> refers to the executable name for the process you wish to change, and 'nnn' represents the new limit.

It is important to note that the new limit will only take effect for a process when it is restarted. The new limits do not apply to already running processes.

The default limit can be also changed globally for all processes by adding the following line to the Prognosis configuration:

SET MEM-SIZE (default, nnn)

where nnn is the new default memory limit.

Note that due to a defect in some versions after adding the above line to the Prognosis configuration and clicking start, you will receive an error message “Invalid process name - DEFAULT”. This error message can be ignored. The default memory limit will still be set correctly.

Note also, that it is possible to remove the memory limit for a process simply set the memory limit to 0 for the process as in the following command.

SET MEM-SIZE (<process>, 0)

This will allow “<process>” to use as much memory as it needs. This should be done with caution as it adds the risk that the Prognosis process may take a lot of memory, as this effectively turns off the in-built mechanism by which Prognosis processes limit how much memory they consume.

View solution in original post

1 REPLY 1
Highlighted
Moderator

Re: What is the default memory limit of Prognosis processes and can it be changed?

What is the default memory limit of Prognosis processes and can it be changed?

Prognosis processes have a self-imposed limit of memory usage of 200MB (note that this is the 'default' value built into the code, and is sometimes over-ridden by out-of-box SET MEM-SIZE settings in the PROGNOSIS configuration).

If a Prognosis process exceeds this default limit, then it will terminate, and log an error such as the following to the wvlog:

"EXTENDED MEMORY LIMIT EXCEEDED"

The default memory limit for any process can be set manually with an entry in the Prognosis configuration that looks like this:

SET MEM-SIZE ( <process name> , nnn )

where <process name> refers to the executable name for the process you wish to change, and 'nnn' represents the new limit.

It is important to note that the new limit will only take effect for a process when it is restarted. The new limits do not apply to already running processes.

The default limit can be also changed globally for all processes by adding the following line to the Prognosis configuration:

SET MEM-SIZE (default, nnn)

where nnn is the new default memory limit.

Note that due to a defect in some versions after adding the above line to the Prognosis configuration and clicking start, you will receive an error message “Invalid process name - DEFAULT”. This error message can be ignored. The default memory limit will still be set correctly.

Note also, that it is possible to remove the memory limit for a process simply set the memory limit to 0 for the process as in the following command.

SET MEM-SIZE (<process>, 0)

This will allow “<process>” to use as much memory as it needs. This should be done with caution as it adds the risk that the Prognosis process may take a lot of memory, as this effectively turns off the in-built mechanism by which Prognosis processes limit how much memory they consume.

View solution in original post

Webinar: Top Ten Predictions in Retail Payments for 2020

Join IR, Celent and your peers as we discuss the top ten predictions for retail payments in 2020 and how evolving your payment solutions will help you stay ahead of your customers’ expectations ...

Join Webinar
Top Liked Members