On Sep 30, 9:41 am, Tim Hoffman <zutes...@gmail.com> wrote: > Maybe you shouldn't use struts, this is a serious suggestion, and should be > considered seriously. > If you have a lightly used small app using a heavy framework then you have > probably made a bad design choice.
I am really some regretting on using java instead of python. I feels google doesn't put enough energy to solve some common problems in java apps, such as slow startup and high memory using. > > If you have long startup times then warmup requests do help enormously, and > in fact are about the only way you are > going to improve the use experience. > > Also if you have such large startup times, then you should probably have > more than one idle instance. > > I would also examine you software stack and see if you can at least serve > the home page/landing page > directly from memcache without starting struts up. > The have on that same page some images that will be loaded after the html is > loaded, and serve these from the > full struts stack. This will mean the front page is loaded fast, and the > images may well trigger additional instances > to be loaded, if they don't load immediately it may not be the end of the > world. > > T -- 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.
