+1 It's critical that the GAE team take these concerns on board. The two selling points of GAE are performance and reliability, yet thanks to the aggressive unloading of idle instances and the constant glitches of the GAE infrastructure, GAE is dramatically underperforming against expectations and of course the competition.
As an IT manager, my observation is this really needs a team dedicating to the systemic problems that GAE currently faces. For example, where is the sandbox in which developers can test their apps against new releases? Where is a list of infrastructure problems/ exceptions and how each one should be dealt with? I'm sure the answer is that the nature of the bigtable/google infrastructure makes it hard to conceive a sandbox. Well somebody needs to focus on what needs to be done to achieve one. Just pretend for a moment that Steve Ballmer and the entire M$ competitive marketing dept. is monitoring this thread. Optimistically yours Roy PS. @Jerome. Throughput and response times are the 2 competing faces of performance. To achieve high throughput through a system, you sacrifice response time, and vice versa. I'm actually fairly confident that the GAE infrastructure can provide the throughput and the Google IO talk about the Whitehouse thingy shows that. What GAE can't seem to provide is reliably good response times, so much so that apps fall foul of the 30 second timeout. On Nov 9, 6:10 pm, James H <james.hollier...@gmail.com> wrote: > Jerome, > > I am concerned about uptime and throughput too. Are there any GAE > sites that boast large volume yet? It would be reassuring to see > stats on such sites that prove the price/performance viability of > GAE. How much traffic are you seeing and at what price and > performance? > > On Nov 4, 2:21 pm, Rusty Wright <rwright.li...@gmail.com> wrote: > > > > > Could you have an automated message (monthly, weekly, whatever) that's > > posted to the GAE groups that informs people about this downtime notify > > group? > > > Max Ross (Google) wrote: > > > Hi Jerome, > > > > There is planned maintenance going on right now. I'd strongly encourage > > > you to subscribe to the App Engine Downtime Notify group where you can > > > learn about these things in advance: > > > >http://groups.google.com/group/google-appengine-downtime-notify > > > > Thanks, > > > Max > > > > On Tue, Nov 3, 2009 at 6:18 PM, Jerome <jerome.mou...@gmail.com > > > <mailto:jerome.mou...@gmail.com>> wrote: > > > > Hello, > > > > Our app has been running on AppEngine Java for 2 months. We are now > > > ramping up on traffic and have enabled the billing feature. We are > > > seeing on a daily basis short (1-2 minutes) outages. Most of the time, > > > this is on the datastore, but these short outages sometimes affect > > > other areas as well, like for instance serving static content. > > > > Today, we are seeing a data store in anomaly. This has been going on > > > for over an our now: > > > Uncaught exception from servlet > > > com.google.apphosting.api.ApiProxy$CapabilityDisabledException: The > > > API call datastore_v3.Put() is temporarily unavailable. > > > We are completely dead in the water... > > > > My 2 questions are: > > > - how/where can we report short outages that are usually not reflected > > > on the AppEngine system status? > > > - what is the AppEngine team plan to ensure a reliable service > > > > Jerome- Hide quoted text - > > > - Show quoted text - --~--~---------~--~----~------------~-------~--~----~ 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-java@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 -~----------~----~----~----~------~----~------~--~---
