Linked by Thom Holwerda on Thu 6th Sep 2012 21:32 UTC, submitted by MOS6510
Benchmarks "During the 4th Semester of my studies I wrote a small 3d spaceship deathmatch shooter with the D-Programming language. It was created within 3 Months time and allows multiple players to play deathmatch over local area network. All of the code was written with a garbage collector in mind and made wide usage of the D standard library phobos. After the project was finished I noticed how much time is spend every frame for garbage collection, so I decided to create a version of the game which does not use a GC, to improve performance."
Permalink for comment 534150
To read all comments associated with this story, please click here.
RE: GC is for scripting
by Treza on Thu 6th Sep 2012 23:20 UTC in reply to "GC is for scripting"
Member since:

There is no reason to try to argue with this

Well, I'll argue.
- Garbage collection is not directly related or "reserved" to interpreted languages and, of course, with JIT compilation...
- All sorts of operating system structures are doing special forms of garbage collection.
- There are all sorts of applications (which are often not games) where doing manual, precise memory deallocation is not practical. The only question is to build an ad-hoc garbage collector or use the general-purpose collector from your favorite langage.
- There are some occasions where GC can be faster than manual memory management, because of memory fragmentation, cache thrashing...

Reply Parent Score: 6