The day is chunked into five pieces. Roughly 5 hours per chunk. The idea is that this way, even if you exhaust one 5 hour period, you'll still be able to serve the remaining 19.
Of course, the real reason is so when they start charging, this way they'll be able to charge you for spike traffic that wouldn't otherwise exceed your daily free quota. Speaking of quotas, I'm really starting to wonder if there isn't something really wrong about their calculation; I did a load benchmark earlier, a simple ab2 -c 10 over a long period of time, after building up the load. Everything was working great, until suddenly, after about 40k requests, a ton of requests started spewing the dreaded cpu warnings. If I'd started a -c 100 or something then I'd understand it, but this was the exact same load pattern over a long period of time, and shouldn't result in any changes whatsoever on the google side of things. A completely stable workload, but still app engine went funky after a while and starting spewing the warnings that the requests never trigger under normal circumstances. If a completely stable workload like that will cause you to go over quota, there's no chance in hell you'll ever get even close to saturating your alotted 5 hour quotas. (Sorry to derail your thread a little bit.) On Sep 4, 11:31 pm, Sylvain <[EMAIL PROTECTED]> wrote: > There are two kinds of quota. > > Documentation : Bandwidth In/out per Day = 10 000 MB > Dashboard : Data Sent/Received = 2 000 MB > > Could you explain the difference ? > > Thank you. --~--~---------~--~----~------------~-------~--~----~ 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 -~----------~----~----~----~------~----~------~--~---
