Hey Niklas, Maybe you could also come up with a simple caching strategy for your rendered templates. Depending on the site, it might make content updates easier later on.
Robert On Fri, May 6, 2011 at 07:14, Niklas Rosencrantz <[email protected]> wrote: > We can measure with yslow to see what we get. 50 ms I understand is > good and 200 to 300 ms approvable. Where I need to optimize is where > there are timeouts (where generating zip files) where responses are so > slow as taking seconds. I measured with yslow and an idea, for > optimization, is that we change a front page to static html and > javascript to bypass the django rendering which we use very little at > certain pages. This will make it faster. My app currently uses python > / django for rendering while the contents aren't very dynamic. So if > we change the pages we can to static html + javascript it should get > very fast. > > Thank you for your comments, > Niklas > > -- > 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. > > -- 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.
