Yeah but where this whole discussion started was that when there's no available instance you can't defer anything, since a cold instance will apparently get the request and due to the change dynamic instances aren't warmed up like they used to be. You're bound to need to do some initialization at that point. And while you could build every single component you're app needs yourself to let it be super duper optimized for App Engine, that will just not justify the amount of work it will take to run a app on App Engine.
IMHO the warm up requests serve their purpose; they warm up the app so that a slightly longer start up time of 10 secs or so isn't that bad. The issue is just that there are now situations where user facing requests end up warming up a instance which sounds like a bad thing, especially if the app is receiving spiky loads. On Saturday, July 21, 2012 11:00:53 PM UTC+2, Brandon Wirtz wrote: > > When I said 1.5 I meant PMF was adding 3.5 you don’t need. PMF takes 5s > the API takes under 1s. I think 2.5s is probably the lowest you can get > and do something truly useful, but it seems that I can do a LOT in 2.5s > (assuming the F4 this thread was about when we started) (well actually > assuming F2, F4’s seem to need 3s no matter what you do) > > But also you don’t have to do anything useful on warmup. So you shouldn’t > serve a ColdStart very often. > > > > I have mentioned before I work to keep everything to under 4s. If my App > Gets to 8s I start slicing it up > > > > I am also 100% confident that if all you do is say “I am up” your warm up > will take under 1.5s for 95% of starts. And that should really do “I am > up” and defer lazyloads of everything you need to be ready to do real work. > > > > > > *From:* [email protected] [mailto: > [email protected]] *On Behalf Of *hyperflame > *Sent:* Saturday, July 21, 2012 1:47 PM > *To:* [email protected] > *Subject:* Re: [google-appengine] Re: Startup time exceeded...on F4?! > > > > I just looked over the logs of a corporate GAE application. It's a very > simple "heartbeat" application; essentially our production applications > have to send a message to it periodically. The message sent is about 500 > characters; the application does some checksum-ing and sends back a JSON > string about 100 characters long. The only external libraries are jars of > twitter4j and the org.json parser. It's really not much more complex than a > Hello World app. > > Looking over the logs, the fastest start time from cold-instance to > first-request-served is 1695 ms (although on average, it needs 2.2 to 2.5 > seconds to cold-start) on a F1 instance. Once the instance is warm, > subsequent requests take, on average, ~150ms to process and send back a > reply. I could probably get that lower if I upgraded to F4. > > On Saturday, July 21, 2012 3:19:21 PM UTC-5, André Pankraz wrote: > > I use getRessourceAsStream an Stream-copy - but you miss the point...it's > a Hello World, done in 5 minutes as test for your post, stripping away all > excuses. > The calls after startup are answered in <80 ms. > That mans that I'm still far above 3 seconds for initializing of an empty > project. I could simply write Hello World into the Stream. > > I could use static...yes...but thats not the point. Some people have > dynamic and user dependand data on each page. > > -- > You received this message because you are subscribed to the Google Groups > "Google App Engine" group. > To view this discussion on the web visit > https://groups.google.com/d/msg/google-appengine/-/TDuwyumyZAIJ. > 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?hl=en. > -- You received this message because you are subscribed to the Google Groups "Google App Engine" group. To view this discussion on the web visit https://groups.google.com/d/msg/google-appengine/-/yM2ywgzd4PIJ. 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?hl=en.
