I'm running a custom modpack on a third-party server host and I could use some help finding a way to reduce memory leaks caused by forge. It's a pretty big pack, 165 mods or so, but the server can handle it with the 6GB RAM it has along with a decent CPU. My computer ran it just fine as a client (rarely used more than 2 gigs and never lagged), but the server hangs after a while, slowly losing what free memory it has. Some research on various forums and logs are telling me it's probably a memory leak caused by the way forge handles dimensions.
As you know, Minecraft at its core has some issues when switching dimensions, but it's optimized enough that you don't really see them come up in vanilla. On a heavily modded forge pack, they can become unbearable. I have around 3 mods that add new dimensions, coming to around 30 registered dimensions in total. When the server starts, I'm told every dimension loads into memory for a moment, before being unloaded almost instantly by forge. It seems this is where the problem is. Other people who have had this same problem report that using a new forge config option fixed it for them, something that adds a delay between when a dimension is determined to have no players inside by forge, and when forge subsequently unloads it. The problem is, this option was added in 1.8 and doesn't exist in 1.7.10, my server version.
Does anyone have any suggestions for reducing the impact of this issue or eliminating it entirely? I've heard placing a tiny chunk loader in every dimension can help, but I'm not sure if keeping ~30 dimensions loaded is a good idea. Thank you in advance to anyone willing to give any advice.