"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."
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.
--
Omnem crede diem tibi diluxisse supremum.
--To view this discussion on the web visit https://groups.google.com/d/msg/google-appengine/-/c_jvZfVchdMJ.
You received this message because you are subscribed to the Google Groups "Google App Engine" group.
To post to this group, send email to google-a...@googlegroups.com.
To unsubscribe from this group, send email to google-appengi...@googlegroups.com.
For more options, visit this group at http://groups.google.com/group/google-appengine?hl=en.
You're pretty observant =). Yes, the filesystem is a distributed virtual filesystem.
T
--
You received this message because you are subscribed to the Google Groups "Google App Engine" group.
To view this discussion on the web visit https://groups.google.com/d/msg/google-appengine/-/vr_DXaIM2YAJ.
This is a great tip. Did you think about crossposting to google-appengine-go?