April 17th, 2020 at 6:36 AM
Ramnode wouldn't be too bad tbh. But you don't really need 2 cores for a server in this case.
Minecraft servers aren't too CPU intensive, or at least don't leak CPU usage most of the time for no reason.
It's usually the RAM that's terribly optimized in server software since most of it runs in the JVM anyway, and JVM garbage collection is, well, putting it nicely, it leaves more to be desired.
That being said, MC server software isn't well optimized for multithreading/multi-core support, because the JRE/JDK both just aren't designed with that in mind. Either the code is written to take advantage of multithreading, or it isn't. In the case of MC servers, it isn't until >=1.14 allegedly, and even then the wiki only lists the possibility with 'some tasks' rather than full optimization.
The good part about the JRE/JDK is that they impose RAM limits on themselves as well. By default, the JRE will run at 1GB of RAM iirc. You can pass arguments like -Xmx2048m to the JRE when you launch the server JAR file to increase the RAM cap.
So BuyVM would technically be a better option for more RAM and less worrying about CPU usage, but honestly either would probably do fine for a server with less than 10 people. If it's a hit after a couple months with a lot of activity, then you could worry about upgrades.
Minecraft servers aren't too CPU intensive, or at least don't leak CPU usage most of the time for no reason.
It's usually the RAM that's terribly optimized in server software since most of it runs in the JVM anyway, and JVM garbage collection is, well, putting it nicely, it leaves more to be desired.
That being said, MC server software isn't well optimized for multithreading/multi-core support, because the JRE/JDK both just aren't designed with that in mind. Either the code is written to take advantage of multithreading, or it isn't. In the case of MC servers, it isn't until >=1.14 allegedly, and even then the wiki only lists the possibility with 'some tasks' rather than full optimization.
The good part about the JRE/JDK is that they impose RAM limits on themselves as well. By default, the JRE will run at 1GB of RAM iirc. You can pass arguments like -Xmx2048m to the JRE when you launch the server JAR file to increase the RAM cap.
So BuyVM would technically be a better option for more RAM and less worrying about CPU usage, but honestly either would probably do fine for a server with less than 10 people. If it's a hit after a couple months with a lot of activity, then you could worry about upgrades.
