Closed Dav1dde closed 9 years ago
I believe this was the issue fixed in hotfix 350 on curse On Mar 8, 2015 8:35 AM, "David" notifications@github.com wrote:
A power buffer with energy (doesn't matter if connected to an energy source) connected to a consumer (tried AE, Auto-Spawner, Sag Mill) causes massive FPS lag (type of cable doesn't matter). Also the position of the buffer doesn't seem to be relevant (even though I only tried it in a radius of ~30 blocks from what you can see in the screenshots).
Version 1.2.1 of FTB Infinity pack (EnderIO 2.2.8.349 according to the changelog https://feedthebeast.atlassian.net/wiki/display/PML/Infinity+1.7+1.2.1)
Disabled output (same if there is 0 energy in the buffer), 60 fps: [image: screenshot from 2015-03-08 13 02 33] https://cloud.githubusercontent.com/assets/255721/6545728/15caf042-c596-11e4-90ea-5302a39d75b8.png
Push or Push/Pull configuration, 10fps: [image: screenshot from 2015-03-08 13 02 57] https://cloud.githubusercontent.com/assets/255721/6545726/15cadc9c-c596-11e4-9829-13a9fd517c1a.png
Same but buffer isn't connected to anything but a consumer (sag mill, milling cobble): [image: screenshot from 2015-03-08 13 18 58] https://cloud.githubusercontent.com/assets/255721/6545727/15caeba6-c596-11e4-815a-79694873c385.png
Console gets spammed with these messages after changing the mode:
[13:17:14] [Client thread/WARN]: Something's taking too long! 'root.gameRenderer.level.updatechunks' took aprox 126.810282 ms [13:17:14] [Client thread/WARN]: Something's taking too long! 'root.gameRenderer.level' took aprox 137.213776 ms [13:17:14] [Client thread/WARN]: Something's taking too long! 'root.gameRenderer' took aprox 138.895257 ms [13:17:14] [Client thread/WARN]: Something's taking too long! 'root' took aprox 151.320182 ms [13:17:17] [Client thread/WARN]: Something's taking too long! 'root' took aprox 101.963695 ms [13:17:17] [Client thread/WARN]: Something's taking too long! 'root' took aprox 104.702209 ms [13:17:18] [Client thread/WARN]: Something's taking too long! 'root' took aprox 105.261023 ms [13:17:19] [Client thread/WARN]: Something's taking too long! 'root' took aprox 100.77037 ms [13:17:20] [Client thread/WARN]: Something's taking too long! 'root' took aprox 114.888671 ms [13:17:20] [Client thread/WARN]: Something's taking too long! 'root' took aprox 118.701574 ms [13:17:20] [Client thread/WARN]: Something's taking too long! 'root' took aprox 100.26886 ms [13:17:20] [Client thread/WARN]: Something's taking too long! 'root.gameRenderer.level.updatechunks.sort' took aprox 100.98288 ms [13:17:20] [Client thread/WARN]: Something's taking too long! 'root.gameRenderer.level.updatechunks' took aprox 101.292286 ms [13:17:20] [Client thread/WARN]: Something's taking too long! 'root.gameRenderer.level' took aprox 111.329372 ms [13:17:20] [Client thread/WARN]: Something's taking too long! 'root.gameRenderer' took aprox 113.214908 ms [13:17:20] [Client thread/WARN]: Something's taking too long! 'root' took aprox 134.7554 ms [13:17:21] [Client thread/WARN]: Something's taking too long! 'root' took aprox 100.794909 ms [13:17:21] [Client thread/WARN]: Something's taking too long! 'root' took aprox 117.646736 ms [13:17:23] [Client thread/WARN]: Something's taking too long! 'root' took aprox 103.417258 ms [13:17:24] [Client thread/WARN]: Something's taking too long! 'root' took aprox 109.535231 ms [13:17:24] [Client thread/WARN]: Something's taking too long! 'root.gameRenderer.level.updatechunks.sort' took aprox 163.192478 ms
Server appears to be fine (no console messages, no ram/cpu spikes)!
— Reply to this email directly or view it on GitHub https://github.com/CrazyPants/EnderIO/issues/2064.
Whoops sorry, latest is 349, not 350. This is fixed already though, in dev builds. On Mar 8, 2015 8:39 AM, "Garrett Spicer-Davis" tterrag1098@gmail.com wrote:
I believe this was the issue fixed in hotfix 350 on curse On Mar 8, 2015 8:35 AM, "David" notifications@github.com wrote:
A power buffer with energy (doesn't matter if connected to an energy source) connected to a consumer (tried AE, Auto-Spawner, Sag Mill) causes massive FPS lag (type of cable doesn't matter). Also the position of the buffer doesn't seem to be relevant (even though I only tried it in a radius of ~30 blocks from what you can see in the screenshots).
Version 1.2.1 of FTB Infinity pack (EnderIO 2.2.8.349 according to the changelog https://feedthebeast.atlassian.net/wiki/display/PML/Infinity+1.7+1.2.1)
Disabled output (same if there is 0 energy in the buffer), 60 fps: [image: screenshot from 2015-03-08 13 02 33] https://cloud.githubusercontent.com/assets/255721/6545728/15caf042-c596-11e4-90ea-5302a39d75b8.png
Push or Push/Pull configuration, 10fps: [image: screenshot from 2015-03-08 13 02 57] https://cloud.githubusercontent.com/assets/255721/6545726/15cadc9c-c596-11e4-9829-13a9fd517c1a.png
Same but buffer isn't connected to anything but a consumer (sag mill, milling cobble): [image: screenshot from 2015-03-08 13 18 58] https://cloud.githubusercontent.com/assets/255721/6545727/15caeba6-c596-11e4-815a-79694873c385.png
Console gets spammed with these messages after changing the mode:
[13:17:14] [Client thread/WARN]: Something's taking too long! 'root.gameRenderer.level.updatechunks' took aprox 126.810282 ms [13:17:14] [Client thread/WARN]: Something's taking too long! 'root.gameRenderer.level' took aprox 137.213776 ms [13:17:14] [Client thread/WARN]: Something's taking too long! 'root.gameRenderer' took aprox 138.895257 ms [13:17:14] [Client thread/WARN]: Something's taking too long! 'root' took aprox 151.320182 ms [13:17:17] [Client thread/WARN]: Something's taking too long! 'root' took aprox 101.963695 ms [13:17:17] [Client thread/WARN]: Something's taking too long! 'root' took aprox 104.702209 ms [13:17:18] [Client thread/WARN]: Something's taking too long! 'root' took aprox 105.261023 ms [13:17:19] [Client thread/WARN]: Something's taking too long! 'root' took aprox 100.77037 ms [13:17:20] [Client thread/WARN]: Something's taking too long! 'root' took aprox 114.888671 ms [13:17:20] [Client thread/WARN]: Something's taking too long! 'root' took aprox 118.701574 ms [13:17:20] [Client thread/WARN]: Something's taking too long! 'root' took aprox 100.26886 ms [13:17:20] [Client thread/WARN]: Something's taking too long! 'root.gameRenderer.level.updatechunks.sort' took aprox 100.98288 ms [13:17:20] [Client thread/WARN]: Something's taking too long! 'root.gameRenderer.level.updatechunks' took aprox 101.292286 ms [13:17:20] [Client thread/WARN]: Something's taking too long! 'root.gameRenderer.level' took aprox 111.329372 ms [13:17:20] [Client thread/WARN]: Something's taking too long! 'root.gameRenderer' took aprox 113.214908 ms [13:17:20] [Client thread/WARN]: Something's taking too long! 'root' took aprox 134.7554 ms [13:17:21] [Client thread/WARN]: Something's taking too long! 'root' took aprox 100.794909 ms [13:17:21] [Client thread/WARN]: Something's taking too long! 'root' took aprox 117.646736 ms [13:17:23] [Client thread/WARN]: Something's taking too long! 'root' took aprox 103.417258 ms [13:17:24] [Client thread/WARN]: Something's taking too long! 'root' took aprox 109.535231 ms [13:17:24] [Client thread/WARN]: Something's taking too long! 'root.gameRenderer.level.updatechunks.sort' took aprox 163.192478 ms
Server appears to be fine (no console messages, no ram/cpu spikes)!
— Reply to this email directly or view it on GitHub https://github.com/CrazyPants/EnderIO/issues/2064.
Ok, so I did some investigating, time spent in level.updatechunks.sort
increases drastically. I am going to try the version from curseforge and report back.
Ok, FTB Infinity 1.2.1 has already build 349, so that doesn't work.
A power buffer with energy (doesn't matter if connected to an energy source) connected to a consumer (tried AE, Auto-Spawner, Sag Mill) causes massive FPS lag (type of cable doesn't matter). Also the position of the buffer doesn't seem to be relevant (even though I only tried it in a radius of ~30 blocks from what you can see in the screenshots).
Version 1.2.1 of FTB Infinity pack (EnderIO 2.2.8.349 according to the changelog)
Disabled output (same if there is 0 energy in the buffer), 60 fps:
Push or Push/Pull configuration, 10fps:
Same but buffer isn't connected to anything but a consumer (sag mill, milling cobble):
Console gets spammed with these messages after changing the mode:
Server appears to be fine (no console messages, no ram/cpu spikes)!