Re:From zero to Go: launching on the Google homepage in 24 h...
by ariwilson on Tuesday December 13, 2011 @10:03PM
(#3350385)
AppEngine instances, unless they're running in a special backend instance, exist in a special containerized machine. These machines are very slow and don't have much RAM - 600 MHz and 128 MB. Based on the source that was posted on the blog, this app was running on a normal instance, as the source did not contain a backends.yaml file.
So it makes sense that a Core 2 Duo running at 2.13 GHz and slow CoffeeScript would be ~2x as fast. My personal experience of running Go code locally (on a Core i5 2500K) versus on a normal AppEngine instance showed a slowdown of around 6x or more.
Re:From zero to Go: launching on the Google homepage in 24 h...
by kamens on Wednesday December 14, 2011 @01:16AM
(#3350887)
This isn't true any more. They recently announced faster frontend instances with more memory (http://googleappengine.blogspot.com/2011/12/app-engine-161-r...), and I'm willing to bet this has been available internally since long before Thanksgiving.
I'd bet money that this app used the beefiest class of frontend instances.
Re:From zero to Go: launching on the Google homepage in 24 h...
by enneff on Wednesday December 14, 2011 @04:13AM
(#3351173)
Nope, it's just a standard app engine set up.
Re:From zero to Go: launching on the Google homepage in 24 h...
by yesbabyyes on Tuesday December 13, 2011 @10:13PM
(#3350416)
I can't argue with that, though I'm running this on just one core (single process).
If I was better with the v8 profiler I would check to see how much time it spends in JS land vs C, since node-canvas is all C, as well as the http parser.
Re:From zero to Go: launching on the Google homepage in 24 h...
by ariwilson on Tuesday December 13, 2011 @10:37PM
(#3350463)
Go runs on a single core unless you start using channels and/or threading libraries. So it should be apples-to-apples.
Re:From zero to Go: launching on the Google homepage in 24 h...
by kinofcain on Wednesday December 14, 2011 @12:00AM
(#3350684)
True, but the base http package handles each request on a different goroutine, so your requests could be handled concurrently:
http://golang.org/pkg/http/#Server.Serve
Though adgar is right, for now I believe you need to specify GOMAXPROCS to utilize multiple cores.
Re:From zero to Go: launching on the Google homepage in 24 h...
by adgar on Tuesday December 13, 2011 @10:46PM
(#3350482)
Go runs on a single core if you use channels anyway unless you specify an environment variable (something like GO_MAX_PROCS). Not sure about threading libraries since I haven't really considered using them in Go. I'm actually curious what people are using them for in Go - maybe games?
Re:From zero to Go: launching on the Google homepage in 24 h...
by 4ad on Wednesday December 14, 2011 @12:28PM
(#3352673)
GOMAXPROCS it is :-).
It's a quick fixup, the runtime will eventually schedule on multiple threads without needing the user to specify anything.
Re:From zero to Go: launching on the Google homepage in 24 h...
by yesbabyyes on Wednesday December 14, 2011 @03:24PM
(#3353435)
I have added the v8 profiler output to the gist. It seems to spend most of it's time in zlib.
Re:From zero to Go: launching on the Google homepage in 24 h...
by jphackworth on Tuesday December 13, 2011 @09:58PM
(#3350372)
To be fair, you loadtested with ab, whereas the author launched his feature on the Google homepage.
Re:From zero to Go: launching on the Google homepage in 24 h...
by yesbabyyes on Tuesday December 13, 2011 @10:04PM
(#3350388)
Sadly I don't have the opportunity. :-)
Re:From zero to Go: launching on the Google homepage in 24 h...
by alexchamberlain on Wednesday December 14, 2011 @02:42AM
(#3351034)
What was the median response time?
All requests in less than 66 ms, mean less than 19 ms.