From zero to Go: launching on the Google homepage in 24 hours
1–10 of 78 posts
Re: From zero to Go: launching on the Google homepage in 24 hours
#2No post body was provided.
Re: From zero to Go: launching on the Google homepage in 24 hours
#3This was interesting because I've never seen Go used in production yet. However, the solution is not optimal for performance (as his benchmarking suggests is one of the goals).
If there is a finite number of possible images and each image takes CPU time to generate, then why not lazy cache the images in a CDN after generating them once?
Re: From zero to Go: launching on the Google homepage in 24 hours
#4This was interesting because I've never seen Go used in production yet. However, the solution is not optimal for performance (as his benchmarking suggests is one of the goals). If there is a finite number of possible images and each image takes CPU time to generate, then why not lazy cache the images in a CDN after generating them once?
The more complicated something is, the more chances for failure there are. Remember, this was only for compositing the image that would be shared to google plus -- the one in the browser is done client-side.
Re: From zero to Go: launching on the Google homepage in 24 hours
#5Quoted post unavailable.
Do consider the virtualization and resource sharing on GAE's server and google main page's views.
Re: From zero to Go: launching on the Google homepage in 24 hours
#6How is Go's websocket support?
I have been thinking Go might be a good choice for a websocket proxy, like node.js is used in Juggernaut (http://flask.pocoo.org/snippets/80/).
Re: From zero to Go: launching on the Google homepage in 24 hours
#7I'm curious to know how many instances were required and what the cost would have been had someone been billed for it.
Re: From zero to Go: launching on the Google homepage in 24 hours
#8This was interesting because I've never seen Go used in production yet. However, the solution is not optimal for performance (as his benchmarking suggests is one of the goals). If there is a finite number of possible images and each image takes CPU time to generate, then why not lazy cache the images in a CDN after generating them once?
This works exactly as you describe - the app sets a cache header on the response and Google's geographically distributed front end servers will serve the cached response. You get all this for free by using App Engine.
Re: From zero to Go: launching on the Google homepage in 24 hours
#9How is Go's websocket support? I have been thinking Go might be a good choice for a websocket proxy, like node.js is used in Juggernaut ( http://flask.pocoo.org/snippets/80/ ).
It's great http://golang.org/pkg/websocket/
Re: From zero to Go: launching on the Google homepage in 24 hours
#10Quoted post unavailable.
Transistor density doesn't guarantee performance increase. Is AppEngine's ability to scale and maintain <60ms consistent with Moore?