While working with dicoogle server we are facing issues for memory
SuketuS opened this issue · 4 comments
Hello @SuketuS. Without more details (JVM version, settings applied, Dicoogle version, plugins used, etc.) it is not possible to understand what can be done to improve the experience here. Note that the JVM is responsible for defining how garbage is collected, and some implementations do not even return freed heap memory back to the operating system (SO).
At first glance, this does not appear to be a problem with Dicoogle itself. If necessary, it is possible to tweak the JVM parameters such as the maximum heap size (-Xmx
).
@Enet4 - We have tried multiple options for the JVM parameters including -Xmx and -XX:MaxMetaspaceSize also --Xmn options but still we are facing issues. where it is getting failed please find the options
java -Xms1650m -Xmx1650m -XX:MaxMetaspaceSize=200M -Xmn400m -Xss1M tried with 200 MB File Uncompreessed with parallel 2 users, however compressed file had better result, can you let me know if any thing we should be know about.
java -Xms1650m -Xmx1650m -XX:MaxMetaspaceSize=200M -Xmn400m -Xss1M
-Xms1650m
would reserve this much heap memory on boot, and to the best of my knowledge, that would never be released to the OS.
Specifically what issues were found when running Dicoogle with these parameters?
can you let me know if any thing we should be know about.
Only that the memory requirements of Dicoogle are directly dependent on the kind of use made. The number and nature of plugins installed, number of images indexed over time, ... all of this can make Dicoogle perform poorly when it does not have enough memory. We generally do not deploy a Dicoogle archive with less than 2GB of dedicated heap memory, and in larger PACS, much more memory is reserved than this.
Closing this issue, as this does not appear to outline a specific and actionable problem with the software. If necessary, you may obtain professional support by teaching out to BMD Software.