If you are loading extra libraries that can slow your load time. Also look at storing variables and other start up information in memcache rather than datastore. I knocked a lot of time off of my startup by trimming the fat and putting all of my start up variables in a single entity rather than having to grab several entities at startup.
From: google-appengine@googlegroups.com [mailto:google-appengine@googlegroups.com] On Behalf Of Tim Hoffman Sent: Thursday, September 29, 2011 5:24 PM To: google-appengine@googlegroups.com Subject: [google-appengine] Re: It is almost intolerable for user experience with 1 idle instances running I have a site, with max idle set to 1, and Min Pending Latency set to 500ms, and I find performance is great. It takes 3-4 secs normally to start the full app up, but through smart caching (I can start a cold instance and serve many pages directly from memcache without starting the full stack in less than <200ms.) I suggest you spend some time having a look at your app startup performance, and profiling your app, rather than spending your time posting the multitude of odd complaints all over the place. Tim -- 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/-/akZjr0DRILYJ. 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. -- You received this message because you are subscribed to the Google Groups "Google App Engine" group. 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.
