The new Task Queue API on Google App Engine(googleappengine.blogspot.com)
googleappengine.blogspot.com
The new Task Queue API on Google App Engine
http://googleappengine.blogspot.com/2009/06/new-task-queue-api-on-google-app-engine.html
5 comments
Not usable for my needs due to a maximum of 10,000 insertions per day and 10 executions per second.
agreed. ever since i started playing around with GAE, i keep getting disappointed at the fine print of its limitations. its almost useless to do any kind of meaningful reporting from the datastore and i'm sure even this task api as you mentioned will keep hammering away at my sanity.
but with that said, i still play with it since i have faith it'll mature into a full platform. and if nothing else, it's a free hosting service for experimental websites, bringing down the barrier to entry officially to zero.
but with that said, i still play with it since i have faith it'll mature into a full platform. and if nothing else, it's a free hosting service for experimental websites, bringing down the barrier to entry officially to zero.
The 10.000 insertions per day is the real limit for now. Otherwise you could execute 24 (hours) * 3600 (s/h) * 10 (tasks/s) * 11 (queues, 1 default + 10 custom queues) = 9504000 tasks per day, which is not bad at all. But as you can only create 10k tasks per day, you cannot even approach this limit.
But note that these quotas are bound to change, they ask for feedback on precisely these issues, task throughput per day and task length, on the Overview page: http://code.google.com/appengine/docs/python/taskqueue/overv...
But note that these quotas are bound to change, they ask for feedback on precisely these issues, task throughput per day and task length, on the Overview page: http://code.google.com/appengine/docs/python/taskqueue/overv...
Agreed. You are already paying for bandwidth (which is _inside_ the datastore, and so should be free). Additional limitations are simply stupid.
Why not just offer persistent threads?
about time
[deleted](1)
Actually, for a while, GAE didn't even have cron tasks. So we were kicking off stuff using silent ajax calls from clients.