[bisq-network/bisq] Java Heap Space - Qubes (#3343)

[cd2357]

@chimp1984 for Qubes, the memory reservation is for the entire OS + applications. I believe it also covers for video RAM, since Qubes has very basic graphics drivers.

If a Qube is setup with some RAM limit, and then if the qube reaches the limit, by default Qubes will "borrow" memory from other VMs (or from the unallocated dom0 RAM) and expand dynamically as necessary. However, to do this, it has a service that pings / checks / adjusts the memory allocation every second, which actually slows Bisq down according to my tests.

Turns out its better to disable this dynamic memory allocation and just set a high enough value for the entire qube, to cover OS + any service + any application (incl. Bisq).

After some experimentation, the settings in #4386 were the most stable and reliable for me. Also, increasing resources beyond that didn't improve Bisq performance (load times, UI responsiveness etc) so those values seem to be the sweet spot.

So for Qubes, I'd say 6GB (and with no dynamic memory mgmt) is probably the best option for a debian Qube that runs only Bisq.

Of course, would be great if others can test and verify this as well, on their setups.

-- 
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/3343#issuecomment-678803798
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.bisq.network/pipermail/bisq-github/attachments/20200823/2ac59a26/attachment.html>