High GC Pressure with Chunk loading / TNT Explosions

[VADemon]

The amount of created garbage seems excessive for what is being done, imho. It's still managable, but I think could be reduced after profiling.

TNT in particular flooding the console with Chunk is already cached, merging with existing ChunkCache.java

Low priority

[DaMatrix]

there shouldn't be all too much being allocated... in the absolute worst case (chunk update packet containing data for every section in a chunk in the nether) it should only cause the following allocations (sizes are assuming a 64-bit hotspot jvm):

• 1x Chunk[16] (144 bytes)
• 16x Chunk (16x40=640 bytes)
• 1x Column (52 bytes)

i'll grant you that the log messages could be reduced, though - there's really no reason to log every time the server sends a partial chunk update.