The problem with a cron every 30 seconds is that it will fire, and start up instances if you have none running - or extra instances if you have one busy - even where there is no "work" to be done.
Maybe you have this non-time-critical work to be done once a day (as is my case also) and you don't care if it takes an hour or more, just want to crunch away at it in the background until it's done and then stop. I haven't debugged my code to see how many workers are spawned...but as I have the same goals as Casy I'll take a look and post back results. -- You received this message because you are subscribed to the Google Groups "Google App Engine for Java" 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-java?hl=en.
