Nothing a well timed CRON job can't help with. I do that with my requests, and keep the engine running warm, but it does come at a cost.
On Sunday, February 3, 2013 10:25:12 AM UTC, gafal wrote: > > After months of complaining about user-facing loading requests, I'm > burned. I'm quitting. > > I'm sad about it. I really enjoyed GAE beside this Critical issue (yes, > this is critical to my customers, so its critical to me and should be > critical to you). > I don't think Google would accept to have it's search engine displaying > results after 20 to 25 seconds to some customers because they reach a cold > instance :-) > Why would we? Why did you leave us in that situation? > > No solution or workaround has ever been provided. We just saw the GAE > development team sticking to its position :-( > Maybe because the scheduler is performing as designed? Customers are not > satisfied so please, redesign it. > > There 's a lot of work awaiting me to get out of GAE framework since I've > been using a lot of the provided services. > I'm really angry about that. That's a lesson hardly learned: avoid > provider locking* even with Google*. > > It was too good to be true. > > Gael > > -- You received this message because you are subscribed to the Google Groups "Google App Engine" group. To unsubscribe from this group and stop receiving emails from it, send an email to [email protected]. To post to this group, send email to [email protected]. Visit this group at http://groups.google.com/group/google-appengine?hl=en. For more options, visit https://groups.google.com/groups/opt_out.
