This post is more than 5 years old
12 Posts
0
1008
March 29th, 2011 02:00
Idle DPA processes keep to much memory
Hello
I am running DPA vers 5.6.0 on a fully dedicated physical windows 2003 server x64 with SP2 and 8 GB of memory
the DB is on an other host.
Everyday we generate Scheduled Reports and after that all the memory and swap is used -> 10.6 GB
the problem is not the use of the memory during the generation of the reports but the fact that the processes used for that are not cleaned out of the memory after the work.
I can see that 3 processes DPA_ReporterWorker.exe are around 1.3 GB + DPA_Publisher.exe around 2.1 GB
Why these 3 processes are still there using space in memory and why the Publisher.exe is not "reset" after the publication of the report ?
Is it possible to configure the settings of DPA to solve that problem ?
To get clean my memory, I restart all the DPA services and the memory used go down to less than 2 GB
Someone has the same problem ?
0 events found
doster1
31 Posts
0
March 30th, 2011 06:00
Hi Arnonev,
The memory in DPA is mostly controlled by Java. Java can be slow to release memory.
When using reporter workers there is the option:
"Soft Memory Limit (MB)"
which does:
Upon a report completion, a worker process will shut itself down if its memory usage is higher than this amount. This allows faster reclamation of memory. If the worker process is using less than this amount, it will wait for the next report.
Thus, if that value is low, such as 256MB, any report that uses more then that memory will allow that worker process to shut down after ti completes, effectively freeing the memory. If that option is high then the memory will remain in use until a report uses more then that amount of memory.
The publisher has only the one memory space and is handled by Java so it will remain in use till Java clears it.
The total amount of memory set for all DPA processes should not exceed the total memory available after OS and other apps.
Hope that helps
Dan