Have you run AppStats yet? It shouldn't take too long, but tasks do have to be stored somewhere, so there is a cost. The optimal solution is likely a hierarchical tree of task creation (1000s, then 100s, then 10s).
On Tue, Apr 6, 2010 at 2:01 AM, conman <[email protected] > wrote: > How long does it take to create task? > > In the docs it is suggested to create one task for each email to send > out (in case of the mass email scenario). > So if I have a list with 10.000 subscribers and I want to inform them > all, then I would have to create 10.000 tasks. > But how many taks can be created within the limitations of one request > without getting timed out? > > Does here exist a rule of thumb? > > Thanks! > Constantin > > -- > 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. > > -- Ikai Lan Developer Programs Engineer, Google App Engine http://googleappengine.blogspot.com | 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]. For more options, visit this group at http://groups.google.com/group/google-appengine?hl=en.
