eeIt's actually stated in the blog: http://blog.golang.org/2011/05/go-and-google-app-engine.html
Also, although goroutines and channels are present, when a Go app runs on App Engine only one thread is run in a given instance. That is, *all goroutines run in a single operating system thread, so there is no CPU parallelism* available for a given client request. We expect this restriction will be lifted at some point. So you can still use go routines, channels, etc - but we're back to like the days of green threads in java where the runtime multiplexes them on a single thread (which is fine). However, we don't get concurrent web requests on the same instance (which is not fine). Consequently, right now, Java Runtime seems to have a pretty significant advantage over the others (even over GO which has concurrency as some of its major advantages). And with instance pricing, it seems like it directly affects cost. -- You received this message because you are subscribed to the Google Groups "Google App Engine" group. To post to this group, send email to [email protected]. To unsubscribe from this group, send email to [email protected]. For more options, visit this group at http://groups.google.com/group/google-appengine?hl=en.
