Hi mback2k, That's correct. The reason for this is that only CPU time is a billed quota - datastore CPU time is a non-billed quota, and there to provide transparency, as well as to prevent accidental abuse.
By enabling billing, you can, of course, use a lot more than 6.5 CPU hours a day. -Nick Johnson On Fri, Aug 7, 2009 at 9:41 AM, mbac...@googlemail.com<mbac...@googlemail.com> wrote: > > Hello everyone, > > it seems like the used Datastore CPU Time is also counted against the > general CPU Time quota. At least that is my guess after watching my > CPU Time usage grow while using the remote API for datastore gets and > puts. Current example quota: > > CPU Time: 19%, 1.20 of 6.50 CPU hours > Datastore CPU Time: 2%, 1.18 of 62.11 CPU hours > > Is this correct? If that is the case, is there any reason for this? I > don't see why I have 62.11 Datastore CPU hours available, while I can > only use ~6.50 of them. And even that is not correct, because every > query requires a minimum amount of general CPU time. > > Thanks in advance. > > Best regards, > Marc > > > -- Nick Johnson, Developer Programs Engineer, App Engine --~--~---------~--~----~------------~-------~--~----~ 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 -~----------~----~----~----~------~----~------~--~---
