Our primary app is on GAE-J, using gaelyk. we also have an experimental version using go. What we've noticed is the ram usage is much much lower. an average GAE-J instance for us, is about 64MB to 72MB.
a typical go instance is about 4MB. It's easy for you to try it yourself for your usage case though, you can just write a couple of simple go functions and deploy it as a different version for your app. there are a few other limitations on the GO side, no namespace support yet, no backend yet, and no concurrent request is a big one. we end up with a lot more go instances vs GAE-J during stress test. On Fri, Sep 9, 2011 at 2:10 PM, awx <[email protected]> wrote: > Do projects written in Go for GAE perform better than Java? Can AppEngine > spin up instances of Go apps more quickly then Java? Is the Go environment > better at serving concurrent requests? > My smallish Java projects are written in such a way that I think they could > be translated in Go in a week or two. Reading the Go press releases, it is > made to sound like apps written in Go would load and begin serving much > quicker than a Java version and limit the loading problems that the Java > version has. Does Go actually deliver any performance benefits? > > "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." > > That sounds bad. > -- Omnem crede diem tibi diluxisse supremum. -- 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.
