If you simply enable billing (even with some super low budget) you will get a significant increase in the number of "free" tasks. http://code.google.com/appengine/docs/quotas.html#Task_Queue
Robert On Wed, Sep 1, 2010 at 18:31, fedex1 <[email protected]> wrote: > I have a question, why have a task queue API limit? If the billing is > on CPU Time, why not let the CPU Time limit handle the quota. > > Here's an example of an application having 25% of CPU left and yet it > ran out of Task Queue API calls. > > Also the idea of app engine (which i like) is small fast processing > tasks, but this task queue API limit seems to penalize the small > tasks. > > CPU Time 75% 4.88 of 6.50 CPU hours > Outgoing Bandwidth 1% 0.01 of 1.00 GBytes > Incoming Bandwidth 6% 0.06 of 1.00 GBytes > Total Stored Data 42% 0.42 of 1.00 GBytes > Recipients Emailed 0% 0 of 2,000 > Task Queue API Calls 100% 100,000 of 100,000 > > Thanks, > Ralph > > -- > 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. > > -- 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.
