Reviving this thread... GAE team: can we get an official comment on this really important issue? Thx
On Sep 2, 1:14 pm, Pol <i...@pol-online.net> wrote: > Our app has been on HRD since the beginning and indeed, the past few > days for the time ever, I saw some timeouts. To be clear, not timeouts > due to contention which we get as expected now and then on > transactions, but timeout on the db itself. > > Our usage patterns haven't changed though, so it would expect it to be > on GAE's end. > > On Sep 2, 10:02 am, JH <ja...@mhztech.com> wrote: > > > > > > > > > I agree on both fronts. > > > Yes, M/S was a JOKE. Once moving to HRD I have not seen a datastore > > timeout at all. > > Until earlier this week I saw a small series of them. I really hope > > we are not going back to what we are all used to on M/S. The old M/S > > problem days were always written off as "well, it's good enough for a > > free service." Now this is hardly free service. In fact it is top > > dollar service, so I'd hope that datastore issue DO NOT RETURN. > > > On Sep 2, 11:10 am, Robert Kluin <robert.kl...@gmail.com> wrote: > > > > I think the point of this post is the trend. At one time master-slave > > > also performed quite well, then we'd see trends where latency > > > increased until a blowup. These graphs show a similar pattern to > > > that: increasing latencies over time. We would like to know that: 1) > > > the trend won't continue, 2) we won't start seeing massive blowups. > > > > As for the SLA, see the exclusions section. SLAs are fairly worthless > > > in my honest opinion anyway, so this probably isn't really something > > > to worry about though. > > > http://code.google.com/appengine/sla.html > > > > Robert > > > > On Fri, Sep 2, 2011 at 10:47, Vivek Puri <v...@vivekpuri.com> wrote: > > > > I will disagree with this post. We were on MS earlier and now on HRD. > > > > While on MS, we used to have datastore timeouts all the time and it > > > > was driving me insane looking at 20-30k error emails come in. After > > > > the move to HRD, everything is stable and there are no datastore > > > > timeouts anymore. I am happy with the move. > > > > > On Sep 2, 11:15 am, Pol <i...@pol-online.net> wrote: > > > >> This is really scary. I'm not so obsessed about the price increase as > > > >> this is something you can "control", but if the HRD starts becoming > > > >> slower and slower, there's absolutely nothing you can do. According to > > > >> these official graphs, it's literally 2X slower than 1 year ago. I'm > > > >> OK with training some speed against increase reliability, the promise > > > >> of HRD, but at some point, you need to draw a line: what tells us it's > > > >> not going to take 500ms to do basic queries a year from now? > > > > >> App Engine team: what's your explanation for this? Are you going to > > > >> put clauses in the SLA to guarantee max average get / put / query > > > >> latencies? Seems to me that if you want to go "enterprise-focus" > > > >> that's needed. > > > > >> On Sep 2, 6:23 am, Mike Wesner <mbwes...@gmail.com> wrote: > > > > >> > Yes, I agree that it won't (can't) get as bad as m/s did get because > > > >> > HRD is awesome. My concern is mostly over how they provision and > > > >> > that > > > >> > the latency is that much higher than it was. Why does the load have > > > >> > such a big impact on latency of datastore query? > > > > >> > We keep very detailed statistics about the latency of our services > > > >> > and > > > >> > its clear by our average latencies that it has creeped up over time. > > > >> > It is roughly 200ms higher than it was when we first moved over to > > > >> > HRD. > > > > >> > Mike > > > > >> > On Sep 2, 8:16 am, Tim Hoffman <zutes...@gmail.com> wrote: > > > > >> > > Hi > > > > >> > > Actually I would disagree on the M/S front, all of my apps are on > > > >> > > M/S and > > > >> > > even despite the recent issues > > > >> > > M/S is way more stable than it was in 2008 and 2009, I mean WAY > > > >> > > MORE STABLE > > > >> > > ;-) > > > > >> > > Thats not to say more growing pains won't be felt. My guess is > > > >> > > with a > > > >> > > supposed imminent exodus of apps, we may say some > > > >> > > performance improvements across the board ;-) > > > > >> > > Rgds > > > > >> > > Tim > > > > > -- > > > > 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 > > > > athttp://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. For more options, visit this group at http://groups.google.com/group/google-appengine?hl=en.
