No, it's unlikely to run both a Minecraft server and a NAS simultaneously on an i3 6006u due to resource constraints.
No, it's unlikely to run both a Minecraft server and a NAS simultaneously on an i3 6006u due to resource constraints.
I've been managing a Fabric Minecraft server and a NAS with an i3 6006u for some time. It worked well with 3-4 players at once, but lag appeared when more than four joined. I rarely use the NAS, so I assume it isn't consuming much resources. At first, I allocated 12GB of RAM to the Minecraft server, and after that, I increased it to 16GB, yet the lag persisted. I've tried adjusting settings, but nothing seems to help. Any suggestions on reducing or eliminating the lag? Also, what mods have you installed so far?
To the best of my understanding, most Minecraft servers run on a single thread unless modified. PaperMC is designed to utilize multiple cores better, but even with an i3 6006U, it remains relatively slow by today’s standards. I’d consider trying PaperMC and tweak the server settings to lower CPU usage—such as limiting how many chunks a player loads at once. The repository you mentioned contains helpful tips for optimizing a Minecraft server; I’d check it out. https://github.com/YouHaveTrouble/minecr...timization
The players are active on the server with many hoppers and redstone setups, which can cause lag. Exploration or world generation may also lead to performance issues. I haven’t encountered a server without noticeable lag during those activities. The mods you have aren’t familiar to me, so it’s hard to judge. It seems RAM usage isn’t the main issue. For modded servers, 6-8GB is typical; vanilla servers with up to five players rarely cause problems with just 2GB. Check your Task Manager for CPU and memory usage—high utilization could indicate a weak processor. You might want to tidy up the MC world or upgrade hardware. The NAS should still function properly. I’m not sure about the specific mods or their effectiveness, but free hosting sites exist; they usually come with some restrictions.
there's an experimental/enterprise thing where they put each region on a separate core to ease the tick thread load on big servers. for example on 2b2t players are so spread out that theoretically you could have a 600 core machine and have every player/clan on their own thread. for small home hosting stuff, players generally arent spread out enough for this to be a thing, unless they just happen to be across a region border from each other. --- on topic: the thing that "lags" on minecraft servers is the tick thread, which as the name implies is a single thread. a few things i can see here that can be a problem: - is chunky running? because that's a mod designed to push ALL of your server's performance to pre-generate large amounts of terrain. - the cpu is a 9 year old mobile chip that in a nas probably doesnt turbo far beyond it's 2GHz base clock. expect single threaded performance to be ass. i mostly host my stuff on an i7-4770, which despite being even older is twice the speed. allocating 12 gigs is probably already well beyond what the cpu could make use for anyways, so memory is not your problem. (i run HIGHLY modded servers on 8GB a lot of the time) you can reduce render distance, you can try optimization mods that focus on cpu-heavy tasks, but nothing is gonna make that potato any faster.
The main issue is it's a dual-core processor and if many players are creating new segments, performance will drop. I'm not very experienced with server-side tuning (though I have plenty of client mods), but the memory usage seems excessive. This isn't a memory problem—it's a CPU one. Make sure Chunky isn't running in the background. Use a chunk pre-generator to build chunks before starting on the server, which will help cut down lag.