That's fixed, thanks. I don't want to mess around too much with the java parameters, as correct GC settings can be environment specific and it's easy to make something that works well for me and badly for others.
2013-01-11 01:46:41 [INFO] [STDOUT] Something's taking too long! 'root.levels.world.entityTick.entities.regular' took aprox 129.625573 ms
2013-01-11 01:46:41 [INFO] [STDOUT] Something's taking too long! 'root.levels.world.entityTick.entities' took aprox 130.619311 ms
2013-01-11 01:46:41 [INFO] [STDOUT] Something's taking too long! 'root.levels.world.entityTick' took aprox 130.720601 ms
2013-01-11 01:46:41 [INFO] [STDOUT] Something's taking too long! 'root.levels.world' took aprox 140.23872 ms
2013-01-11 01:46:41 [INFO] [STDOUT] Something's taking too long! 'root.levels' took aprox 257.216034 ms
2013-01-11 01:46:41 [INFO] [STDOUT] Something's taking too long! 'root' took aprox 291.909293 ms
2013-01-11 01:46:42 [INFO] [STDOUT] Something's taking too long! 'root.levels' took aprox 173.959129 ms
2013-01-11 01:46:42 [INFO] [STDOUT] Something's taking too long! 'root' took aprox 190.939098 ms
2013-01-11 01:46:42 [INFO] [STDOUT] Something's taking too long! 'root.levels' took aprox 181.823961 ms
2013-01-11 01:46:42 [INFO] [STDOUT] Something's taking too long! 'root' took aprox 204.211762 ms
2013-01-11 01:46:42 [INFO] [STDOUT] Something's taking too long! 'root.levels' took aprox 183.831011 ms
2013-01-11 01:46:42 [INFO] [STDOUT] Something's taking too long! 'root' took aprox 187.799428 ms
2013-01-11 01:46:42 [INFO] [STDOUT] Something's taking too long! 'root.levels' took aprox 145.464943 ms
2013-01-11 01:46:42 [INFO] [STDOUT] Something's taking too long! 'root' took aprox 147.202553 ms
2013-01-11 01:46:42 [INFO] [STDOUT] Something's taking too long! 'root.levels' took aprox 151.634964 ms
2013-01-11 01:46:42 [INFO] [STDOUT] Something's taking too long! 'root' took aprox 153.109858 ms
2013-01-11 01:46:43 [INFO] [STDOUT] Something's taking too long! 'root.levels' took aprox 122.987931 ms
2013-01-11 01:46:43 [INFO] [STDOUT] Something's taking too long! 'root' took aprox 124.002247 msThe debug log saves its information to a file in the debug folder in your server directory, I'll need to see that. Although that is definitely very slow...
Looks like there's a patcher issue, it's breaking the IntegratedServer class by modifying the MinecraftServer class, will need to look into that later. For now, getting TT working on clients isn't top priority.
Actually, that report isn't a full report. You need to pastebin the contents of tickthreading.log.
It didn't work. Logs: http://pastebin.com/rfaamqzhedit: Fixed-ish-maybe, can you try repatching with the latest build? If it gives an error, it'll actually be a useful one at least
That error down at the bottom is impossible without something not related to TT which is incorrect - can you try without optifine?
The first error report seems to be cut off at the bottom
I'm unable to fix CC as the log was incomplete due to a bug with the logging
Try /ticks, it will list the slowest ticking chunks. TT actually is the slowest thing there! Although you are still managing ~20TPS. Lag spikes (and also slightly lower than 20 TPS) may be caused by the world saving minecraft does every 45 seconds. In one of the recent builds I added the option to change the save interval, you may want to try that.
More threads are used than cores because some time will be spent waiting for other things to finish, and not doing any work. For example, if two tick regions next to each other are ticking, they will never tick entities next to each other at the same time. Adding more threads means that while that's waiting, another tick region can be ticked.Question:
It appears to be that the algorithm for automatic threads is cores * 3 / 2
So in my case, 2 * 3 / 2 = 3
Since there are now 4 threaded things (Entities, Tile Entities, World Tick, Chunk Tick) does this mean one of them is being killed off at random in order to fit into 3 threads?
I don't completely understand how multi threading works - so I'd appreciate some information
From what I understand, there can be more then one thread per core - but the ultimate benefit comes from being able to run them on multiple cores.
Would I need to increase threads to 4 in order to make all of the threaded features actually work?
Try replacing only the EnergyNet.class and EnergyNEt$Something.class files in IC2 from the new IC2 jar before patching. (Or put it into the IC2 jar in the TickThreadingBackups directory and repatch)