The lag spikes caused by the GC running when using this mod are much larger compared to not using this mod. I compared Sodium + Lithium + Starlight vs Sodium + Lithium + Starlight + C2ME.

This is generally caused by Minecraft itself and gets amplified by multi-threading. We are working on allocations reduction but fixing this issue is counted as an optimization, not a bug fix.

Any update on this?

Not to necro a post, but I am able to reproduce this 100% of the time on a raspberry pi 400. The gc spikes cause regular ticks to take 170% to sometimes 1300% of their average usual times.

Which ends up making the server completely unplayable due to the poor hardware, if the only change I make becomes removing this mod, the server never shows overloaded messages.

Unfortunately I may confirm it on 1.19.3 on Radxa Rock 4C+ (with 4GB of RAM). Without C2ME (and with DimThread, and other performance mods such as FerriteCore or Starlight) performance is better - while chunk loading is slower (due to single threaded operation), lag spikes introduced with (I guess GC) are too high for comfortable game.

This is still being worked on. We are in the process of significantly reducing allocs.