Troubleshoot High Memory Usage After Server Load

When GcGo Isn't Enough

If your server still uses excessive memory after startup despite running GcGo Mod, the issue may lie elsewhere.

Identify the Real Problem

1. Check mod count — Very large modpacks may still require significant memory even after cleanup

2. Review player activity — Once players join, memory usage increases naturally due to loaded chunks, entities, and player data

3. Monitor over time — Memory leaks from individual mods cause gradual increases; GcGo only cleans startup bloat

4. Verify mod compatibility — Some mods allocate memory inefficiently; GcGo can't optimize poorly-written code

What GcGo Cannot Fix

• Memory leaks in individual mods (ongoing memory growth)
• Necessary memory for active gameplay (chunks, players, entities)
• Inefficient mod design or configuration
• Insufficient allocated heap size

Next Steps

If memory remains high:

• Increase your server's maximum heap allocation
• Remove unnecessary mods
• Check mod configuration files for memory-intensive settings
• Consider using additional optimization mods alongside GcGo