On Sat, Jun 20, 2009 at 5:00 PM, Thomas<[email protected]> wrote: > > Some initial thoughts using the task queue api: > > 1. It is very easy to create a chain reaction if you don't know what > you are doing :P
Indeed it is :-P > 2. Using the queues with the dev_appservery.py is very nice such that > you can test things out and see how things get queued. > > 3. Would like to see flush queue option (or something) in the > production server, as well as to look at the queue. We don't have this right now, but will certainly add this eventually. In the mean time I would encourage you to file this on the issue tracker. > 4. My (horrible) first try at queues with production data spawned a > lot of tasks, most of which now I wish I could just remove and start > over. One thing you can do is pause the queue. Another is to push a new version of your app that has a very simpler handler for the URL the tasks are using; that way it will quickly eat through all of the dangling tasks. > 5. It seemed like I generated 10x tasks then what I was expecting, not > sure if that is my mistake, but it didn't seem to have this order of > magnitude when I tried with development data, so I am not sure if that > is my fault or what. > > 6. Currently my queue is stuck and not progressing, again, not sure if > that is my fault or not. > > Thanks again, the API itself it drop dead simple and fun. Glad to hear! --~--~---------~--~----~------------~-------~--~----~ 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 -~----------~----~----~----~------~----~------~--~---
