On Tuesday, 21 October 2014 at 07:18:28 UTC, ROOAR wrote:
So the latest Minecraft apparently runs really really poorly
because of the GC.
And it is running on Java desktop. The supposedly "fast" GC of
Java can't handle the game anymore--
https://www.reddit.com/r/programming/comments/2jsrif/optifine_dev_minecraft_18_has_so_many_performance/
Take that GC fanatics
D needs more action you know.
How did that work in previous releases? The previous Minecraft
releases were much less memory hungry. The original Notch code
(pre 1.3) was allocating about 10-20 MB/sec which was much more
easy to control and optimize. The rendering itself needed only
1-2 MB/sec and was designed to minimize memory waste (reusing
buffers, etc).
Why is 1.8 allocating so much memory? This is the best part -
over 90% of the memory allocation is not needed at all. Most of
the memory is probably allocated to make the life of the
developers easier.
tldr; When 1.8 is lagging and stuttering the garbage collector
is working like crazy and is doing work which has nothing to do
with the game itself (rendering, running the internal server,
loading chunks, etc). Instead it is constantly cleaning the
mess behind the code which thinks that memory allocation is
"cheap".
I could quote the entire post, but the bottom line is: this issue
has nothing to do with the GC. Crappy code is crappy code. So
your OP is just pointless troll.
