I don't disagree that the Payment Page is horribly broken. And Google Wallet is horrible, and a "notify me if quota is estimated to be reached in 6 hours" wouldn't be an awesome feature.
But like your CSV input. We'd put that through a validator before it went "live" and that validator might only be another app that says "Hey did this error" but nothing changes in a Live deployment without humans. For small things. we'd hope that 50x would still do us. If you don't want to be down have a high budget. If you don't want to wake up broke one morning because of a bug in your code, set the budget low. Assume you can only change your budget between 9 and 5 EST on week days. Which sucks, but I make the same assumption with a number of my clouds If for no other reason than every so often the limiting factor is I need to call a Credit card company to say "Hey I really do want to give Amazon more than $3000 today. Yes I realize I gave them $2500 every day this week, but today I want to give them $6000." From: [email protected] [mailto:[email protected]] On Behalf Of Jeff Schnitzer Sent: Wednesday, March 07, 2012 1:49 AM To: [email protected] Subject: Re: [google-appengine] Re: Huge number of datastore reads? On Wed, Mar 7, 2012 at 1:08 AM, Brandon Wirtz <[email protected]> wrote: > The worst of it: we looked like rank amateurs in several ways, but perhaps If you are going to run with the training wheels on, don't be surprised when you hit a pot hole and your back tire just spins with you going nowhere. Sorry Brandon, you're way off-base here. There's no excuse for buried land mines like this to exist. Nobody realizes that you get frozen out of the system for 30+ minutes at a time until you actually get screwed by the system. And no matter what you think you've set your budget to, something can come along and blow it. For example, every night I process a significant volume of CSV data downloaded from a technically unsavvy organization. They seem to delight in finding new and interesting ways to break my (popular third-party) CSV parser. The latest was a name field containing "Blah Blah, Jr" - you can guess what that did. After a few rounds of this I have hacked my parser enough to consume just about any garbage they can feed me. Nevertheless, there were quite a few nights early on where this error caused a large task-queue-driven data processing operation to fail. With the default retry schedule, it quickly ate through my (seemed-to-be-generous-at-the-time) billing quota. Fortunately my technically unsavvy organization is sufficiently clumsy that these problems came up early. If they were only slightly more clever, these issues might not surface until long into production, when it really mattered. As those of us in Javaland were reminded today, GAE fails us every now and then. It needs to fail gracefully. The default over-quota message is WAY more embarrassing than "XYZ is experiencing technical difficulties" - how can we override it? If...you are pretty sure you don't have a bug that is going to cost you millions of dollars... ...then you are delusional :-) Jeff -- 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.
