Geyser causes very high RAM/CPU — what's the solution?
Geyser adds real overhead because it translates protocols for every Bedrock player in real time. If crossplay is pushing your RAM or CPU high, there are several ways to bring it back down.
Why Geyser is heavy
Every Bedrock player's traffic has to be translated between Bedrock and Java, and that work scales with your player count. Crossplay servers simply want a bit more headroom than Java-only ones.
Ways to reduce the load
- Make sure you have RAM headroom — crossplay servers want more (see our sizing guides).
- Keep Geyser and your server software updated — efficiency improves a lot over time.
- Lower view-distance if Bedrock render load is heavy.
- For large networks, consider running Geyser in standalone mode on a separate small server.
Tip: If usage is extreme with only a few players online, that points to a config or version problem — share a spark report so it can be diagnosed.
Frequently asked questions
How much extra RAM does crossplay need? More than a Java-only server of the same size. See our sizing guides, and open a ticket if you'd like help picking a plan.
Should I run Geyser standalone? For large networks, yes — putting Geyser on its own small server offloads the translation work from your main server.
Usage is huge with barely any players — normal? No. That usually means a config or version issue. Generate a spark report and share it via ticket.