Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Docs/Description - Mention where C2ME doesn't help #288

Open
robog-two opened this issue Mar 25, 2024 · 2 comments
Open

Docs/Description - Mention where C2ME doesn't help #288

robog-two opened this issue Mar 25, 2024 · 2 comments
Labels
bug Something isn't working status: more info needed Further information is requested

Comments

@robog-two
Copy link

Hi!

I think this mod is amazing! However, it may be worth including in the mod description what situations the mod will hurt more than help. For example, running a Minecraft server on my Raspberry Pi 4, the extra threads created for world generation brings it to its knees! (it does just fine without the mod) I couldn't tell you if this is due to low memory, or due to few cores (it's a quad-core ARM cpu), or due to low per-core performance. Either way, it may be worth mentioning that the mod doesn't really help low end hardware, only servers with breathing room in terms of cores/memory/GHz to achieve faster world generation.

More testing as to how many cores/what clock speed/how much RAM is required for this mod to speed up may be necessary for a more accurate warning, but I don't really have the time or hardware to do that.

Best,
robog

@robog-two robog-two added the bug Something isn't working label Mar 25, 2024
@robog-two robog-two changed the title Description - Mention where C2ME doesn't help Docs/Description - Mention where C2ME doesn't help Mar 25, 2024
@ishland
Copy link
Collaborator

ishland commented Mar 26, 2024

The default configuration should at least perform the same as vanilla if not better assuming that:

  • The CPU can run an all-core load without thermal throttling at the base clock for an extended period of time
  • Configured thread count is no more than the actual CPU thread count (especially on Windows)

However, if the above conditions are not met, it is considered as a hardware or software configuration error and should be resolved by the server admin.

I've seen people running this on Raspberry Pi 4 without issues. Please provide logs so that we can further investigate.

@robog-two
Copy link
Author

Don't have time to get the logs for you at the moment but I can at least confirm this WAS with the default configuration - I did not touch the configuration.

It may be an issue with docker, in that cores are not detected properly. ARM CPUs do not hyperthread (this is an Intel proprietary design). So in that case you'd probably want LESS threads than CPU cores to give the kernel and OS some breathing room.

As for thermals, from my testing previously that should not be an issue but once I get better logs I can check for sure.

This was on Fedora CoreOS (linux) which, if any one else is interested in reproducing, is the same base as Fedora Server with an immutable configuration for automatic updates. So they should perform about the same.

Raspberry pi was the 4GB model but had no memory issues w/o the mod installed, so if it is a GC thing, it's this mod.

Running inside of docker using this https://github.com/itzg/docker-minecraft-server

Sorry I couldn't be of more help, will get you more logs ASAP. Also, it depends on the configuration of the Raspberry Pi, mine is certainly not optimal for minecraft performance specifically but it suits my needs (auto updates = no less fussing with the server)

@ishland ishland added the status: more info needed Further information is requested label Mar 26, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
bug Something isn't working status: more info needed Further information is requested
Projects
None yet
Development

No branches or pull requests

2 participants