Replies: 1 comment 3 replies
-
I personally use the container as is but assign the following
Curious what you have for swapiness as unless specifically changed, many default to something like 60 as a default. Also, how is your system doing in terms of actual memory usage (like from It might be possible that there are some java arguments that could be tuned to try to optimize memory a bit more for your specific scenario but if you're swapping, the system thinks there is memory pressure so you have to look at the system holistically and not just on specific processes. I forget exactly how the kernel decides what gets sent to swap but it wouldn't surprise me if the controller is being sent to swap because the JVM is allocating memory it's not actively using so it's the best (least impactful) swap candidate. |
Beta Was this translation helpful? Give feedback.
-
Controller Version
5.15.20.10
Describe Your Issue or Question
I noticed that I was approaching current SWAP limits on my docker host (currently 1GiB) and when looking at various container use it seems to be almost all the omada container. I previously ran this on bare metal and didn't pay as close attention, but don't recall it being very swappy. I'm wondering for larger home use (10 devices, 100 clients) what settings you use for memory, swap, etc (or if not limiting, what does your system use usually)? The default compose file doesn't have any resource settings... would something like this help or be bad for this stack?
Top swap use:
Expected Behavior
Would expect it not to be swappy or use swap (generally that's bad for java) - but maybe I'm misguided here?
Steps to Reproduce
Run with the default compose file
How You're Launching the Container
Container Logs
MongoDB Logs
Additional Context
No response
Beta Was this translation helpful? Give feedback.
All reactions