I haven't really done any measurements, although I plan to later on, on my second RasPi. I do know that the lighting thread runs rather slow on ARMs, there's already a github issue for that. Also the mob code could be much improved (it currently collects a mob census on every world tick, instead of keeping the census and updating it when mobs are spawned / destroyed.
I haven't overclocked my RasPi, because it runs 24/7 and I was concerned with damage due to prolonged CPU stress. Also there doesn't seem to be any need for the overclocking, the server does run nicely.
I suppose the best way to find out is to try it out for yourself, I do believe that the server should be usable for 5 players.
Oookay, did some basic measurements. Without any players, the server is using 3 % CPU and 170 MiB of memory (most of it probably already committed to chunks and unloaded yet). When a player connects, the server spikes into 100 % CPU for a short while (3 seconds), possibly because of all the chunks that are being streamed to the client. Then the CPU sits at 10 % while the player moves around little, occasionally going up to 60 % when a few new chunks need to be loaded and sent to the client. THe RAM usage stays within the 170 - 180 MiB margin all the time, confirming the primary suspicion of already-committed memory.
I haven't overclocked my RasPi, because it runs 24/7 and I was concerned with damage due to prolonged CPU stress. Also there doesn't seem to be any need for the overclocking, the server does run nicely.
I suppose the best way to find out is to try it out for yourself, I do believe that the server should be usable for 5 players.
Oookay, did some basic measurements. Without any players, the server is using 3 % CPU and 170 MiB of memory (most of it probably already committed to chunks and unloaded yet). When a player connects, the server spikes into 100 % CPU for a short while (3 seconds), possibly because of all the chunks that are being streamed to the client. Then the CPU sits at 10 % while the player moves around little, occasionally going up to 60 % when a few new chunks need to be loaded and sent to the client. THe RAM usage stays within the 170 - 180 MiB margin all the time, confirming the primary suspicion of already-committed memory.