Since we are on this topic. Task Quota has 3 items: Task API Calls: 100,000 Task Stored Task Count: 1,000,000 Task Stored Task Bytes: 104M // This one is understood
Since it does not appear possible to enqueue a new task without invoking a Task Queue API, it seems like API Call Count is the choking point. In other words 100K of API calls is not enough to hit Stored task Count of 1M ever. The only situation in my mind Stored Task Count can come into play is if Tasks remain pending from before Quotas were refilled. Could you please explain? Thanks On Oct 14, 10:49 am, "Ikai Lan (Google)" <[email protected]> wrote: > I believe this are garbage collected. This'll be a gating issue for us > before we release - it would be pretty bad if this caused quota denials. > > -- > Ikai Lan > Developer Programs Engineer, Google App Engine > Blogger:http://googleappengine.blogspot.com > Reddit:http://www.reddit.com/r/appengine > Twitter:http://twitter.com/app_engine > > On Wed, Oct 13, 2010 at 8:51 PM, Eli Jones <[email protected]> wrote: > > Ikai, > > > On occasion I execute thousands of tasks. Works great too. > > > But, it seems like Task Queue Stored Task Bytes does not reset very > > quickly. > > > Currently my Task Queue shows (and I have 0 Tasks in any Queues.. and > > haven't for over 10 minutes): > > > Task Queue Stored Task Count 136,603 of 200,000,000 > > Task Queue Stored Task Bytes 124,768,866 of 104,857,600 > > > Recently I just ran under 1,000 tasks, and a few hours ago I was running > > many other tasks.. but they all run and finish within 3 minutes.. so it > > seems strange that the Stored Task values keep increasing.. > > > How often are these values reset? Are they not really reset as soon as the > > Tasks in a queue are finished or purged? > > > Thanks for any information. > > > Eli > > > On Wed, Oct 13, 2010 at 5:42 PM, Ikai Lan (Google) < > > [email protected] <ikai.l%[email protected]>> wrote: > > >> Hey everyone, > > >> We're working on moving Task Queues out of labs/experimental for an > >> upcoming release slated for November. One of the requirements for doing so > >> is to better enforce the Task Queues storage quota. The documentation > >> describes this quota as storage for data for tasks that have not yet > >> executed: > > >>http://code.google.com/appengine/docs/quotas.html#Task_Queue > > >> Currently, this quota is not enforced, and it is possible for applications > >> with backed up task queues to exceed this quota without running into quota > >> denials. Check your admin console's quota page for your application to see > >> if you are reaching or exceeding this quota. If so, you'll have the > >> following options: > > >> 1. Allocate more storage quota to taskqueue storage by updating: > >> - total_storage_limit in queue.yaml for Python applications > >> - TotalStorageLimit in queue.xml for Java applications. > >> Note: you may need to buy more disk quota if there's not enough > >> quota for datastore, blobstore and taskqueue storage altogether. > > >> 2. Fix backed up queues using one of the options below. You will recognize > >> these as queues with high numbers of tasks (typically >2000). > >> - Purge backed up queues (an easy button click in admin console's > >> Queue Details page for the queue). > >> - Increase the execution rate and let your app work through the > >> backlog. To do this, edit queue.yaml (or queue.xml for Java apps) and alter > >> the rates on the queues. You can set a higher bucket size than the default > >> (currently 5) to maximize throughput. > >> - Reduce the rate at which new tasks are added to queues. This > >> will involve some editing of app code. > > >> It can take a few hours to update the admin console after the quotas have > >> been updated. > > >> We'll post a reminders to the App Engine blog as well as to this thread as > >> the release nears. > > >> -- > >> Ikai Lan > >> Developer Programs Engineer, Google App Engine > >> Blogger:http://googleappengine.blogspot.com > >> Reddit:http://www.reddit.com/r/appengine > >> Twitter:http://twitter.com/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 [email protected]. > >> To unsubscribe from this group, send email to > >> [email protected]<google-appengine%[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]<google-appengine%[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.
