News for hackers. Stuff that matters.
Re:Visualising the Go garbage collector by jerf on Friday July 11, 2014 @08:57AM (#8019866)
It looks like the sample benchmark is of the "godoc" tool in http server mode. In this mode, godoc serves a local website that is a near-clone of http://golang.org/ , which is particularly useful because the local "Packages" tab will contain not just the standard library, but all local packages, including the ones you've downloaded and the ones you are writing [1]. Consequently, the program is, on average, doing nothing. To get those graphs at all, I assume he was clicking around in the served web site, because otherwise I'd expect nothing at all to happen.

So we're not looking at a big website serving dozens of requests per second... we're looking at a program with a relatively expensive startup (and in this case I mean "relatively" literally; in absolute terms it's quite fast in my experience, I've never been able to start the program and ALT-TAB to my web browser and load a page before it's ready), which then twiddles its thumbs.

To compare it against an active Java server program, you'd basically collapse the whole graph into about 2 or 3 seconds worth of activity, if that.

[1]: Incidentally, another example of "something simple Go does that intuitively feels like it shouldn't be a special thing because it feels like every language ought to already have such a thing, except that when you go looking for it, you can't find it". It doesn't sound like an all-in-one API documentation of everything you've got locally would necessarily be that especially useful, but it really is.

Re:Visualising the Go garbage collector by 4ad on Friday July 11, 2014 @12:15PM (#8020929)
Note: an idle godoc does almost nothing, this is godoc started with the indexing option.