I have been pondering the same question, since my instance start times are anywhere between 5 and 15 seconds, with the average approaching 10 seconds (GAE Java). This seems to be on the slow side; I found a few older articles with some tips on this topic:
http://www.listry.com/blog/2010/03/google-app-engine-cold-start-guide-for http://www.small-improvements.com/app-engine-performance-tuning The two biggest factors seem to be: 1) Reduce dependencies to a minimum (i.e don't use heavyweight frameworks). 2) Reduce app specific initialization activity to a minimum (i.e. don't load a ton of resources from disk or the data-store each time the app is initialized) I don't do any app specific initialization, and the only framework I use is Objectify. I do use a few third party libs such as Apache commons, etc. Also, I am not sure if certain issues still apply; for example, is the loading of individual class files still a big drag on cold start times? On Tuesday, June 5, 2012 9:51:51 AM UTC-4, Cesium wrote: > > Hi Takashi, > > You wrote: > >> ...it is very important to keep your application fast even on the >> loading request in order to minimize the damage to your system during such >> serving changes. > > > Can you refer me to some guidelines to keep my application fast even on > the loading request? > I have no idea what the implications are. > > David > > -- 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/-/e46MZFMKm4oJ. 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.
