For our site we actually have a build process for our CSS templates at application start. This way we can have different domains depending on the configuration (testing, prod, dev), and it all works with the same templates. They are compiled at application start rather than being served dynamically because the context never changes and we can take advantage of nginx's speed at serving static content.
Craig Younkins On Fri, Jan 6, 2012 at 5:31 PM, Jonathan Vanasco <[email protected]>wrote: > make sure to bench in terms of concurrency and try to send a long term > cache control header. > > the problem i experienced years ago under similar setups (mod_perl and > mod_python) was this: the render/etc times were really nothing or the > items were served 'raw' by the app -- but all the js / css / img etc > items resulted in dozens of requests to the apps per page viewed. > because the apps had inherent overhead and would max out at , for > example , 20 concurrent requests instead of thousands like nginx could > easily handle, once person viewing a page could essentially lock up > the server for a 30-90 seconds. i believe this was one of the larger > issues affecting the performance of trac installs a while back as > well. > > -- > You received this message because you are subscribed to the Google Groups > "pylons-discuss" 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/pylons-discuss?hl=en. > > -- You received this message because you are subscribed to the Google Groups "pylons-discuss" 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/pylons-discuss?hl=en.
