I'm not sure if I understand the usage correctly, but I have a function I wrote with the intended use of being a deferred task. The task is designed in a way to "fan out" hundreds (and those can also create hundreds more) of other tasks for some data mining I need to accomplish. There is usually about 30 minutes of intensive data mining that is accomplished over 4500 tasks every time I need to do this.
When I ran this under my normal app, I would quickly eat up all my CPU time (about $10 enabled billing/day). I looked into backends and thought my use case was a good fit, so I added the _target='backend_id' parameter to all my deferred task calls but my CPU time is still being used up quickly and on top of that I'm paying for the backend up time as well (I cut $5 to backends and $5 to CPU). Am I wrong to assume that my deferred tasks should just use my backend instance up time and not my normal CPU time? This was my hope in trying to reduce the daily cost of my application. Are deferred tasks the wrong way to utilize backends? I am open to any suggestions or advice that can be provided. Thanks in advanced. -Prateek -- 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.
