Hi, Thanks. I have filed an enhancement request to support multiple datacenters. Please vote if you'd like to see improved latencies :)
http://code.google.com/p/googleappengine/issues/detail?id= "GAE apps are currently pinned to one datacenter (with failover). Please provide an option for VMs in multiple locations in the world to keep request latencies low. Current round-trip times of requests are really high from many locations (on a simple http ping ~100ms in the US, ~200ms in EU - presumably higher from Asia). Presumably this would also reduce bandwidth costs for Google. This may introduce some new consistency issues to be aware of (eg. memcache would need to split, the DS "eventual consistency" may become more "eventual", etc), but would still be quite simple to manage for developers. (As a simpler workaround, being able to configure the geographical location for an app would be helpful - at least one could partition the app by geography with different URLs)." Thanks, Viktor On Feb 5, 1:42 pm, "Nick Johnson (Google)" <nick.john...@google.com> wrote: > Hi phracktle, > > Posts like this may be better suited to the google-appengine group, since > they're not Java specific. > > On Thu, Feb 4, 2010 at 7:29 PM, phraktle <phrak...@gmail.com> wrote: > > Hi, > > > Can the Google team please shed some light on the issue of multiple > > datacenters in various geographical locations pertaining GAE? I would > > like to understand what characteristics and what level of guarantees > > to expect from a GAE app, and didn't find any docs or posts on this... > > > 1. Is static content delivered by a geographically distributed CDN? > > Would make sense for latency and international bandwidth costs. > > If you specify caching settings, yes, your content may be cached at the > edges of our network. > > > > > 2. Does GAE launch VMs of a single app in multiple datacenters? Same > > as above - latency would be quite bad for some geographical locations > > without this. > > No, currently we're single-homed, with failover. > > > > > > > > > 3. If VMs are distributed, what's the deal with memcache? If it's > > distributed, does/can it split into distinct partitions? How does that > > affect atomic operations, such as increment, or things like grabTail? > > > 4. If there's geographical distribution, how does it affect Datastore > > performance and latencies? > > > My current (disappointing) impression based on latencies is that GAE > > VMs are not geographically distributed, based on the latencies. But > > would be good to get some clear information on this. > > > In general, it would be quite useful to be able to monitor VMs better, > > eg. how many VM launches took place, where. This would provide more > > insight into the operation and performance of the app... (This may > > also be a stepping stone toward the "pay to keep some VMs warm" topic, > > an often requested feature - at least we could see ) > > > Thanks, > > Viktor > > > -- > > You received this message because you are subscribed to the Google Groups > > "Google App Engine for Java" group. > > To post to this group, send email to > > google-appengine-j...@googlegroups.com. > > To unsubscribe from this group, send email to > > google-appengine-java+unsubscr...@googlegroups.com<google-appengine-java%2B > > unsubscr...@googlegroups.com> > > . > > For more options, visit this group at > >http://groups.google.com/group/google-appengine-java?hl=en. > > -- > Nick Johnson, Developer Programs Engineer, App Engine > Google Ireland Ltd. :: Registered in Dublin, Ireland, Registration Number: > 368047 -- You received this message because you are subscribed to the Google Groups "Google App Engine for Java" group. To post to this group, send email to google-appengine-j...@googlegroups.com. To unsubscribe from this group, send email to google-appengine-java+unsubscr...@googlegroups.com. For more options, visit this group at http://groups.google.com/group/google-appengine-java?hl=en.
