We experience the exact same behaviour on our server, using 1.7.5; 1.8 is untested. From what I've observed, this issue occurs only on "old" chunks. i.e. chunks that were generated way before 1.7.4 - iirc they all were generated (explored) in 1.2 EDIT: The lagy-chunks first occured in 1.7.4 and still exist in 1.7.5
When inside such chunks, the CPU utilization skyrockets on one core, the framerate drops, but the memory utilization (as shown in MC) is no different from normal.
Michael Lenz
We experience the exact same behaviour on our server, using 1.7.5; 1.8 is untested.
From what I've observed, this issue occurs only on "old" chunks. i.e. chunks that were generated way before 1.7.4 - iirc they all were generated (explored) in 1.2
EDIT: The lagy-chunks first occured in 1.7.4 and still exist in 1.7.5
When inside such chunks, the CPU utilization skyrockets on one core, the framerate drops, but the memory utilization (as shown in MC) is no different from normal.