I'm pretty sure the cron service simply calls a url and reports whether it got status code 200 or not. Other than that, there shouldn't be much difference. You should try profiling two requests, one from cron and one from a browser, and comparing them to see what the real difference is.
On Jun 23, 6:25 pm, Mariano Benitez <mari...@benitez.nu> wrote: > Hello, > > Now that I got cron, I moved something I used to do in a normal > handler to use a cache and refresh every 5 minutes. > > What I discovered now is that what used to take 400ms in the normal > handler is now taking 800+ms in the cron handler. (I do the exact same > thing, really) > > I don't know if cron handlers are being cached or since I do it not > very frequently I have to pay that price. > > Thanks --~--~---------~--~----~------------~-------~--~----~ 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 -~----------~----~----~----~------~----~------~--~---
