On Monday, July 01, 2013 00:35:45 David wrote: > Am 30.06.2013 22:53, schrieb SomeDude: > > On Sunday, 30 June 2013 at 20:47:17 UTC, Adam D. Ruppe wrote: > >> On Sunday, 30 June 2013 at 20:37:16 UTC, SomeDude wrote: > >>> It seems indeed that the automatic memory management is a major > >>> performance killer > >> > >> Eh, I'd say it is D's gc implementation specifically that is the > >> biggest worry rather than the concept. I think the .net gc is > >> seriously like 10x faster than D's implementation. > > > > Yes, yes, you're right. However, not allocating at least in Phobos is > > one of the surest way to get near optimal performance, not to mention > > it's always more satisfying when you know that your program doesn't > > monopolize Mb of RAM to do even the simplest task. > > Wow, I don't care if it does, especially if it is only a simple task. > Memory is there to be used. If I want to avoid memory useage, I wouldn't > be using D.
For simple stuff, I really don't care much about how much memory a program uses as long as it's not an outrageous amount. So personally, I don't find it more satisfying to know that my program doesn't monopolize MB of RAM. And honestly, I have enough RAM on my system, that you _can't_ monopolize RAM if you're not talking in GB. However, memory usage matters a _lot_ for programs that need to be really performant (especially when they're larger programs), and having the GC kick in a lot due to how much memory you're using can be a real performance killer. So, being able to minimize the memory footprint of your program is critical, because there are cases where you _really_ care, but there are also plenty of cases where you really don't. - Jonathan M Davis
