Describe the bug

When the server starts, it shortly crashes, due to tps being too low/one tick taking too long. The crash report show that it may have something to do with autocrafting. Debug profiling shows that the enderio me conduits may also have something to do with it. Removing the me controller at start also didn't solve the problem. (It also didn't take much tick time)

I also made an issue on the enderio issure tracker: SleepyTrousers/EnderIO-1.5-1.12#5295

To Reproduce

1. Start server with the culprit world and wait until it crashes

Expected behavior

The server to start normally and have a resonable tps

Additional context

• Modpack Mod List + Versions(I am the Modpack Author): https://pastebin.com/Xn7PgDzn
• Bedug Profiling: https://pastebin.com/rNBgrWk3
• Crash Report: https://pastebin.com/kQp8Pstt
• Latest Log: https://gist.github.com/JoeJoeTV/293858231befbf37b3ed4dae960bc803

Environment

• Minecraft Version: 1.12.2
• AE2 Version: rv6-stable-7
• Forge Version: 14.23.5.2874
• Dedicated Server running on debian

Don't use colossal chests, they are major performance issue. Probably on top of Lazy AE2, too.

Ok, thanks, also figured out that the world would load again after removing sand from the level maintainer from lazy AE2. Is Lazy AE2 really taht laggy, we're just using the crafting machines in our autocrafting.

In my experience most AE2 addons have major issues. Be it in regards of performance or just introducing bugs or weird behaviour. Especially smaller ones, which only add a very limited amount of features, usually haven't left the proof of concept phase as well as provide something, which is already in AE2 itself but might need 2 instead of 1 blocks or similar.