I think deferred tasks is an excellent use case for backends. That's how I use my backend as well. Can you confirm from your logs that your tasks are indeed being processed on the backend? In the drop down for app versions, there's a special "version" which is named after your backend. Select that to check your logs specific to the backend. Also, I'm assuming the reason you're blowing through your budget is because you're spanning out multiple, possibly hundreds of instances. Can you find out how many instances get spawned for your deferred tasks? Can you find out how many backend instances are being spawned, if the backend is indeed being used for your tasks? Finally, when you configured your backend, what did you set as your "instances" parameter in backends.yaml? I don't know what the default is, but it is likely "unlimited". In your case, a instance of 1 or 2 sounds sufficient, but you'll have to play around with that, based on how much queueing occurs for your tasks.
On Tue, Oct 4, 2011 at 12:06 AM, Gerald Tan <[email protected]> wrote: > I believe CPU time will no longer be billable after the new pricing is out > > -- > You received this message because you are subscribed to the Google Groups > "Google App Engine" group. > To view this discussion on the web visit > https://groups.google.com/d/msg/google-appengine/-/Crry-7yTG4QJ. > > 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.
