Corticon uses heap memory to process decision service calls.
As the service is called, memory is allocated to process the request, and then is free for GC after the request finishes.
We have no evidence of memory leaks, however if a service is quickly processed its memory would be allocated and freed in a short moment and is then available for GC.
The memory usage is very dependent on the size/complexity of the rules and the size of the data. XML uses more memory the java objects.
IF there is a backlog of requests (say because there are more server instances then processors) then a case where a large amount of memory is being consumed may occur.
Corticon uses heap memory to process decision service calls.
As the service is called, memory is allocated to process the request, and then is free for GC after the request finishes.
We have no evidence of memory leaks, however if a service is quickly processed its memory would be allocated and freed in a short moment and is then available for GC.
The memory usage is very dependent on the size/complexity of the rules and the size of the data. XML uses more memory the java objects.
IF there is a backlog of requests (say because there are more server instances then processors) then a case where a large amount of memory is being consumed may occur.