To avoid these long "loading requests" you can either make your app faster to load or keep it warm by pinging a page with a cron job, say every minute. Cron jobs will only work on the default (live) version so I wrote a PingTaskServlet that simply places another task in the queue and finishes.
On Dec 30 2009, 2:13 pm, Derek Battams <de...@battams.ca> wrote: > I've written an incoming mail handler and it works, that is, it does > what I want it to do, but it runs slow, very slow. However, I'm not > sure why it's so slow because I'm using theQuotaServiceto time how > long the doPost() method of my email handler servlet is running and > it's returning 0.00 CPU seconds and 0.04 API seconds, yet the logs > routinely report the requests taking over 10000ms. > > I notice that if I fire two emails in rapid succession at my app then > usually the first one reports as taking 10000+ ms to run then the > second one will run in under 150ms, which is confusing me even more. > It's almost like the app is having to spin up on every email it > receives, but 10+ seconds for the spin up seems way too long. Is > there something I should be watching out for when writing incoming > email handlers?
-- 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 google-appengine-j...@googlegroups.com. To unsubscribe from this group, send email to google-appengine-java+unsubscr...@googlegroups.com. For more options, visit this group at http://groups.google.com/group/google-appengine-java?hl=en.
