Hi Ikai, Considering your recommendation is there any progress in providing an easier migration path for existing applications?
On Mon, Jan 31, 2011 at 5:51 PM, Ikai Lan (Google) <ikai.l+gro...@google.com<ikai.l%2bgro...@google.com> > wrote: > I'm going to let someone else answer this question, but we are recommending > that all new applications use High Replication datastore. Datastore latency > spikes are virtually non-existent if your application uses HR instead of > master-slave. > > -- > Ikai Lan > Developer Programs Engineer, Google App Engine > Blogger: http://googleappengine.blogspot.com > Reddit: http://www.reddit.com/r/appengine > Twitter: http://twitter.com/app_engine > > > > On Sat, Jan 29, 2011 at 10:25 PM, Natalie > <nataliegladstone...@gmail.com>wrote: > >> Hello, >> >> We are at the planning phase on a new App Engine project, and we are >> unsure about the choice of Master/Slave and High Replication. >> >> About our site: >> The site is expected to get a lot of hit (Around 50-200 QPS.). >> Around 20% write and 80% read. >> Minimal outrage a must. Will lose a lot of clients if outrages are too >> frequent. >> >> We would love to hear from fellow App Engine developers of their >> experiences with HR. >> >> In particular we want to know: >> 1) Recently the M/S datastore has very high latency for query. How’s >> your experience in HR? >> 2) What’s your approximate of the HR datastore availability? Is it >> close to 99.9%? >> 3) How is the read/write performance of HR datastore? Would love it >> if >> you could share some statistics. >> 4) How much does the cross datacenter synchronization issue affect >> the >> performance of your site? Please see this link about the issue: >> >> http://groups.google.com/group/google-appengine/browse_thread/thread/5fc3b6a4366de62f/4b4d23e924b7b136 >> >> It would be great if you could share your experience with us and other >> App Engine developers. >> >> Thank you very much. >> >> -- >> 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-appengine@googlegroups.com. >> To unsubscribe from this group, send email to >> google-appengine+unsubscr...@googlegroups.com<google-appengine%2bunsubscr...@googlegroups.com> >> . >> For more options, visit this group at >> http://groups.google.com/group/google-appengine?hl=en. >> >> > -- > 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-appengine@googlegroups.com. > To unsubscribe from this group, send email to > google-appengine+unsubscr...@googlegroups.com<google-appengine%2bunsubscr...@googlegroups.com> > . > For more options, visit this group at > http://groups.google.com/group/google-appengine?hl=en. > -- *Jeff Schwartz* -- 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-appengine@googlegroups.com. To unsubscribe from this group, send email to google-appengine+unsubscr...@googlegroups.com. For more options, visit this group at http://groups.google.com/group/google-appengine?hl=en.
