Read operations had no quota prior to November 7th (technically unlimited). Now they do - only 50k free read operations allowed per day. Before November 7th, read operations may have been implicitly limited by CPU Hours. They contributed to CPU time, and CPU time was limited to 6.50 hours. Now "CPU Time" isn't itself limited directly. It has been loosely replaced by "Instance time" - the time a front-end instance (or a backend) stays up, whether it is consuming CPU or not (it won't consume CPU during I/O operations such as data store read/writes, URL fetches, etc).
On Wed, Nov 16, 2011 at 3:45 AM, Mr. Schtief <[email protected]> wrote: > Hi, > > Am i the only one that encounters so many overquotas since the billing > change? Before billing change all my quotas where running at 1 to 5 % for > one day. now its goind to 100% especially for read operations in some hours. > > so is the free quota reduced so much? > > thx for any help > > schtieF > > -- > You received this message because you are subscribed to the Google Groups > "Google App Engine" group. > To view this discussion on the web visit > https://groups.google.com/d/msg/google-appengine/-/GA_6KfGBP00J. > 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.
