"100% of our production system is now running Go"

Re:"100% of our production system is now running Go" by luriel on Friday August 31, 2012 @10:54AM (#4459969)

> The right way to avoid GC pauses in a GC'd language is to avoid generating garbage; e.g. with free lists.

And Go makes it much easier to avoid generating garbage than pretty much every other GC language around, already "by default" Go code tends to generate dramatically less garbage than for example Java, and when you care, you can further fine tune it to produce even less garbage.

[ Parent | on HN ]

Re:"100% of our production system is now running Go" by mogrim on Friday August 31, 2012 @01:49PM (#4460812)

Genuine question, from ignorance: How does Go create less garbage than Java? I can certainly appreciate that a lot of the common frameworks used in JEE development may be memory-hogs, but the language itself?

[ Parent | on HN ]

Re:"100% of our production system is now running Go" by vetinari on Friday August 31, 2012 @02:58PM (#4461147)

just iterating:

  for (Object o: collection) {
  }

causes memory allocation.

If you are interested, android team at had several talks at Google I/O (not just 2012) about optimizing memory usage.

[ Parent | on HN ]

Re:"100% of our production system is now running Go" by mogrim on Saturday September 01, 2012 @06:46AM (#4463334)

Cheers, will check those out.

[ Parent | on HN ]