Ray wrote: " I am still having around 1% percentage of datastore timeout from any kind of datastore accesses like a simple get_wih_id()."
I have not seen this. If you and others are seeing 1% get_by_id()s failing due to timeouts, it needs to be diagnosed by G. stat. Be sure to report it. If it is a common issue, and remains so with G. acknowledging its part and parcel of their PaaS, then it really is time to move to AWS for me. -stevep On Apr 5, 6:26 pm, Ray <[email protected]> wrote: > No one regret moving to HRD not because its great, instead its the M/S > sucked too bad lately. 30 minutes download evey week is a disaster for > any kind of app hosting on it. > > At the mean time, HRD still isn't flawless. I am still having around 1% > percentage of datastore timeout from any kind of datastore accesses like a > simple get_wih_id(). It is slower than M/S and cost more (the /G cost is > now the same since Google raised the price for M/S too, but the slower > respond still cost more on instance number) > > The most stinky part is how Google advertise it as a 100% up time service > when it is generating more exceptions than most shared MySQL hosting > outside. I know I know, its about scalability. But how many apps are > having hundreds or thousands of DB access every second that can benefit > from its scalability which can compensate the constant flaw? > > > > > > > > On Thursday, April 5, 2012 4:46:57 AM UTC+8, Robert Kluin wrote: > > > I think this is a really good idea. It will encourage people with > > apps to move, and help further persuade new apps to not use > > master-slave. I have not spoken to anyone who regretted the move to > > high-replication. > > > Robert > > > On Wed, Apr 4, 2012 at 15:42, Chris Ramsdale <[email protected]> wrote: > > > Hey App Engine Users, > > > > Almost 4 years after launch, we’ve seen fantastic growth both in Google > > App > > > Engine and the apps that run on it. And although the Master/Slave > > Datastore > > > was a big part of our early success, it's time to announce the > > deprecation > > > of the Master/Slave Datastore in favor of the High-Replication Datastore > > > (HRD). HRD has provided us with higher availability and better, more > > > predictable performance. Many upcoming features will be HRD-only and we > > > strongly encourage you to migrate all your applications as soon as > > possible > > > using the migration tools found in the Application Settings tab of the > > > Administration Console. The deprecation period will follow the guidelines > > > set in our terms of service. If you have any questions or concerns, > > please > > > contact us at [email protected]. > > > > Chris > > > > Product Manager, Google App Engine > > > > -- > > > 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. -- 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.
