Max size Induction Matrix (18x18x18) Causes Server Lag
See original GitHub issueThis isn’t the first Mekanism multiblock to cause server lag. We’ve previously taken down all the salination towers for a similar reason, but the extent that the Induction Matrix causes lag is far, far greater.
TPS: 14.1 Single Entity | Time/Tick | % TileEntityInductionPort {2792,59,5431}:0 | 2.036 | 4.927 TileCustomCable {2793,76,5446}:0 | 1.010 | 2.445 TileCustomCable {2793,76,5433}:0 | 0.996 | 2.411 TileEntityInductionPort {2808,59,5432}:0 | 0.976 | 2.361 TileEntityInductionPort {2807,74,5448}:0 | 0.975 | 2.359 Chunk | Time/Tick | % 0: 174, 339 | 6.168 | 15.034 0: 174, 340 | 5.074 | 12.367 0: 175, 339 | 4.070 | 9.920 0: 175, 340 | 4.044 | 9.856 0: 0, 9 | 0.805 | 1.961 All Entities of Type | Time/Tick | % TileEntityInductionPort | 16.361 | 39.878 TileCustomCable | 2.092 | 5.098 TileConduitBundle | 1.654 | 4.032 TileMultipartContainer$Ticking | 1.321 | 3.220 monster.EntityWitch | 1.001 | 2.439 Average Entity of Type | Time/tick | Calls TileEntityInductionPort | 0.824 | 2800 TileEntityWeatherStation | 0.116 | 88 tile.TileController | 0.088 | 987 EntityButterfly | 0.070 | 141 TileExternalStorage | 0.067 | 705
The difference between having that thing loaded or not is night and day. Since the lag seems to be concentrated at the induction ports, look to the code that adds energy and see what an 18x18x18 matrix filled with Ultimate cells does. I think you’ll find a serious inefficiency there.
This is with the latest—as of today—version. The Avant 3 pack got it’s 1.16 update JUST to make sure this hadn’t been fixed.
Issue Analytics
- State:
- Created 7 years ago
- Comments:10 (3 by maintainers)
Just because you CAN build it that size doesnt mean you SHOULD.
Since 18x18 is slightly larger than a chunk size, border crossings are unavoidable.