When starting a server on debian 7 and 8 it allocates 21.0GB of memory, regardless of how much you declare as the Java xmx. This is a problem because the swap of a machine is filled very quickly.
Once the swap is used StarMade never stops using it until you restart the server, causing huge performance issues.
Description
Description
Details
Details
- Task Type
- Bug
Testing Results
- Affected Gamemode(s)
- none/unspecified
- Reproducible
- Yes
- Last tested (version)
- 0.199.152
- Category
- none/unspecified
Hardware/Software/System
- OS-Specific
- No
- Hardware-Specific
- No
- Video Card Vendor
- uncertain
Steps to reproduce
Start StarMade server from command line, use a tool like htop to check VIRT memory allocation.
Serverconfig (server.cfg)
<replace this line with the file content>
Clientconfig (settings.cfg)
<replace this line with the file content>
Java Version (64bit)
java version "1.8.0_101"
Java(TM) SE Runtime Environment (build 1.8.0_101-b13)
Java HotSpot(TM) 64-Bit Server VM (build 25.101-b13, mixed mode)
Event Timeline
Comment Actions
-Feedback-
Okay, there is some overhead in the JVM, but several GB over the set limit is unusual, and may be not physical memory being used, but rather swap memory that for some reason exceeds the size of our testserver by several times.
What are the exact memory arguments passed to the server?
(xmx, and xms value)
Comment Actions
please try proper powers of 2 for the values.
xms2048M and Xmx8192
would be good values.
Any non-power of too can cause issues in the behaviour of the memory mangement and overshoot to the next power of two.
Comment Actions
-Invalid-
Problem solved by increasing available ram.
Not the optimal solution but worked.