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 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.
