02-10-2012, 01:36 AM
I'ts not really massive, but still is quite a lot 
On my QuadCore, the tick thread was hogging one core all the time (-> 25 % total CPU) before the change. After the change, the thread is using only about 5 % of the total CPU. Both values were measured with 1 player on the server, 17 chunks viewdistance.
This means that it now runs at least 5 times faster, maybe even more, because a thread can't run faster than one-core-at-a-time.
Note, however, that this was a debug build. In a release build this needn't be so noticable.
On my QuadCore, the tick thread was hogging one core all the time (-> 25 % total CPU) before the change. After the change, the thread is using only about 5 % of the total CPU. Both values were measured with 1 player on the server, 17 chunks viewdistance.
This means that it now runs at least 5 times faster, maybe even more, because a thread can't run faster than one-core-at-a-time.
Note, however, that this was a debug build. In a release build this needn't be so noticable.