It's currently mostly for organisational purposes, to have separate logs and to notice spikes in the dashboard graph better. The backend can probably handle 360/m because as you notice from the logs it takes much less than 100ms to send the mail out. The problem though is that it sends out much much slower by setting a low enforced rate even though there were no errors on the backend in the past 7 days.
And in a related matter: I've uploaded new code yesterday and there was a syntax error which I didn't notice. The backend got constant start requests at a very fast rate. 2011-08-17 08:46:32.180 /_ah/start 500 70ms 70cpu_ms 0kb instance=0 2011-08-17 08:46:32.076 /_ah/start 500 71ms 70cpu_ms 0kb instance=0 2011-08-17 08:46:31.966 /_ah/start 500 66ms 46cpu_ms 0kb instance=0 2011-08-17 08:46:31.864 /_ah/start 500 69ms 46cpu_ms 0kb instance=0 2011-08-17 08:46:31.766 /_ah/start 500 77ms 46cpu_ms 0kb instance=0 Maybe this should be throttled? And once the error was fixed and the pending mails were send out, the backend set a very low rate of about one mail every 30 seconds. This seems like a mistake to me because it wasn't the task (or class) that failed, which justifies to progressively lower the task rate as it's currently done, but rather the backend itself. -- You received this message because you are subscribed to the Google Groups "Google App Engine" group. To post to this group, send email to google-appengine@googlegroups.com. To unsubscribe from this group, send email to google-appengine+unsubscr...@googlegroups.com. For more options, visit this group at http://groups.google.com/group/google-appengine?hl=en.
