server freezes when a bedrock player joins, due to excessive CPU and RAM usage

Describe the bug

Basically what the title says, the server CPU and RAM usage skyrockets when a bedrock client joins the server, causing the server to freeze and kick everyone after some time. Then, the server has to be killed because it doesn’t get fixed after everyone has been kicked, it just remains frozen.

To Reproduce

I don’t know what to put here

Expected behaviour

Normal CPU and RAM usage.

Screenshots / Videos

Normal CPU and RAM usage:

CPU and RAM usage when a Bedrock client joins:

Server Version and Plugins

Main server: [16:45:55 INFO]: This server is running Mohist version 1.12.2-225 (MC: 1.12.2) (Implementing API version 1.12.2-R0.1-SNAPSHOT, Forge version 14.23.5.2855) Plugins: WorldGuard, WorldEdit, Essentials, LightCleaner, Skript (and many addons), Citizens, BungeeGuard, Vault, Luckperms Mods: WorldEdit, Terra++, CubicChunks, CubicWorldGen, JourneyMap, Terramap

BungeeCord Proxy: Waterfall-1.17-448 Plugins: BungeeGuard, Floodgate (#19), Geyser (#781), ServerListPlus, ViaBackwards, ViaRewind, ViaVersion

Geyser Dump

https://dump.geysermc.org/CeHjcjeYDCkaq9Bl9pMG7VghFiDFMuyp

Geyser Version

Build #781

Minecraft: Bedrock Edition Version

1.17.1

Additional Context

No response

[PIZZAAXX]

I’m waiting for my host to change the startup command since I can’t change it directly.

[Camotoy]

More specifically: the exact issue here is very convoluted. ViaVersion takes sub-chunk packets from pre-1.16 and makes them into multi-block packets. Geyser currently has to take this information and divide it into 4096 individual packets. It would just be better in this case to have a Cubic Chunks designed for the 1.17 protocol - my vanilla 1.17 client didn’t have a fun time either. If someone would like to take a stab at improving this scenario, by all means, feel free, but the core team going to leave this specific scenario as-is.