[bisq-network/bisq] Bisq using up too much memory on Linux even after closing (#3918)

[Stan]

To sum up, I agree the biggest problem on Linux is off-heap memory growth.  Your adding the MaxRAM jvm option reduced resident memory > 50%

The next experiment should be adding

    export MALLOC_ARENA_MAX=4
    export MALLOC_MMAP_THRESHOLD_=131072

to the bisq-desktop and bisq-daemon startup scripts;  _this requires no changes to the binaries_.
If testers don't see any performance drag from this after using this setting for X days, they might try to save another ~100 or so MB RAM by setting the jvm's start & max heap size: 

    -Xms820m  -Xmx820m

820 MB should be sufficient, and I think Linux bisq users would be happy to see a ~ 1.0 GB resident memory size after starting bisq with an empty data dir.  (When we started investigating, bisq's resident memory size was growing to ~ 4.8 GB.  So problem not solved, but this is a significant improvement.)

Regarding the Java Heap:  I certain JavaFX 11 has leaks, and their dev team has been fixing them in a version we cannot use yet. Can't do much about that yet.  There are probably other on-heap leaks, but I have not been able to identify with certainty.  



-- 
You are receiving this because you are subscribed to this thread.
Reply to this email directly or view it on GitHub:
https://github.com/bisq-network/bisq/issues/3918#issuecomment-607198677
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.bisq.network/pipermail/bisq-github/attachments/20200401/ca6aac5a/attachment-0001.html>