 |
|
|
|
|
|
|
Knowledge
Base::
PretonService memory usage
Issue:
PretonService memory usage is high
Solution:
The PretonSaverClient and
PretonCoordinator (server) services are both built as .Net components, and as such
all memory management is controlled by the .Net runtime (similar to java),
the .Net runtime will utilize it's memory heap until it reaches a peek and
then call it's
'Garbage
Collection' to free up memory and handles, this 'peek' threshold is dynamic
and relies on the available system's resources, this behavior allows the
.Net runtime to utilize system resources as long as they are not needed for
other task. You can view this behavior buy running a memory intensive
process and see that the PretonSaverClient foot print is reduced to around:
700k-1.5Mb
Memory, ~15Mb VM, 500 Handles, and 16-20 Threads.
The fact that windows task manager shows high memory allocation, does not
mean that Preton services are using that memory allocation, when the computer
requires the memory for other applications, the .NET garbage collection is
being called and the allocated memory is being freed for other usages.
|
|
|
|
|
|
|
|
