On Thu, Sep 8, 2011 at 7:17 PM, Jon McAlister <[email protected]> wrote: > > I understand that the worry, and I agree we should do better. There > are indeed several things which can be happening here. The usual > suspects are request spike, app moved to another machine, or datastore > latency spike, but there are other things that can trigger this as > well. Basically, it's actually a complex distributed system under the > hood, but we're trying hard to make it appear to not be. But at places > like this, details are bleeding through the abstraction layer.
One way to fix some of these problems would be to raise the free quota to 25 instance hours. Greg D thought this was a good idea when the new pricing was first announced, but it seems to have been forgotten about: On Wed, May 18, 2011 at 4:55 PM, Gregory D'alesandre <[email protected]> wrote: > On Wed, May 18, 2011 at 1:57 AM, 风笑雪 <[email protected]> wrote: >> >> Hi Greg, >> >> Can you raise On-demand Frontend Instances free quota to 25 Instance Hours >> per day? >> >> The small apps have very low traffics in average, but sometime (maybe >> several minutes) it may use more than 1 instances to handle burst traffics, >> so that they will got OverQuotaErrors at the end of the day. > > Its a good point, we'll look into this. Thanks for the suggestion! > > Greg Another way to fix some of this might be to enable people to allocate resources within the free budget allowance themselves. So for example, some of the 9 hours currently available for backends could be used for front ends, or vice versa. Arguably, it would better highlight some of the advantages of the billing interface. -- 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.
