Hi Neal On Dec 2, 10:00 am, NealWalters <[email protected]> wrote: > Tim, > How would I go about your one suggestion: "Some other strategies you > can adopt to shrink startup times is trying > to defer some of your imports until you need to use the stuff. "
Its difficult to say stright off the bat, without some idea of what sort of app you are using and what sort of stack. But some strategies that might work are if you greeting page for the app is fairly static you could stick it in memcache, and server it directly with a custom handler that only imports code appengine. You can get this serving your start page on a cold start up in < 300ms most of the time. > > I have what I would consider a very large code base, just not many > users at this time. My main.py has probably 200 imports in it. I have some big apps (well I think so) about 18,000 loc not including some of my re-used libraries and about 30 models, lots of adapter registrations and it normally starts up in < 5secs. Whoa, 200 imports that raises some alarm bells with me ;-) > But if I remove the imports, it won't compile... the WSGI statement > cannot map the URL page name to the appropriate code. > You might want to look at alternate more compact url mapping schemes. Provide some more info and I am sure some of us can help improve those startup times. Rgds Tim > Neal -- You received this message because you are subscribed to the Google Groups "Google App Engine" group. 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.
