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.

On Tue, 21 Oct 2014 07:18:26 +0000
ROOAR via Digitalmars-d <digitalmars-d@puremagic.com> 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.
wow! you are the man! you are the savior! sorry, my Guru, can't write to you anymore: i need to remove GC from all my projects!

"Maybe the biggest and the ugliest problem is the memory allocation. Currently the game allocates (and throws away immediately) 50 MB/sec when standing still and up to 200 MB/sec when moving. That is just crazy."

Wonder how much better that would be if Java had proper value types. The idea of allocating on the heap for every single Vector3f makes me sad.

> wow! you are the man! you are the savior! sorry, my Guru, can't write
> to you anymore: i need to remove GC from all my projects!

I know! It is great being me!

I had to do it, D forum was putting me to sleep with its discussion of Postblits and environmental errors. Phfff like those matter.

On Tue, 21 Oct 2014 07:44:09 +0000
ROOAR via Digitalmars-d <digitalmars-d@puremagic.com> wrote:

> I had to do it, D forum was putting me to sleep with its discussion of Postblits and environmental errors. Phfff like those matter.
yeah, this was... refreshing morning. ;-)

On Tuesday, 21 October 2014 at 07:37:06 UTC, Kapps wrote:
> "Currently the game allocates (and throws away immediately) 50 MB/sec when standing still and up to 200 MB/sec when moving. That is just crazy."

In D this rate of allocation would make GC take 100% of CPU time. The fact that Java survives it with just some frame rate loss shows how great its GC is.

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.

More like: take that you smart business people who buy a bloated piece of **** for 2.5 BILLION $$$

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.

> 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.

 This issue sure does seem to crop up in GC world, wonder why. Oh well.

 That company with $2.5 billion can't find competent Java engineers lolz!

 Memory isn't scaling at the rate compute is. I wonder how much worse this issue will be in 5 years. Oh well, let's just write more Java code:)

>In D this rate of allocation would make GC take 100% of CPU time. The fact that Java survives it with just some frame rate loss >
>shows how great its GC is.

 So:
Java GC is turd
D GC is wretched turd

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.

Part of my work is to teach people to use tools like VisualVM, Eclipse MAT and similar and to clean offshore code before it gets integrated into customer premises.

Bad code is bad code, regardless of a presence of a GC.

Unfortunately a GC that removes bad written code is yet to be invented.

--
Paulo