I just ran across this comment on Apache and dynamic sites
http://blog.webfaction.com/handling-the-digg-effect-on-a-standard-shared-hosting-account:
"This confirmed what we've thought for a long time: Apache rocks,
provided you use the following simple tips:
* Use "Timeout 30" and "KeepAliveTimeout 3" (or similar values):
this will insure that no client will block Apache's threads or
processes for too long (otherwise the number of Apache
threads/processes will skyrocket). If you're hosting with us, these
values are set by default in our main Apache server for you.
* Serve as much content as possible statically: even if you use a
dynamic framework such as Rails, Django, TurboGears or mod_python, you
should try to serve your static data (images, stylesheets, ...)
statically (ie: serve them from your web server directly and save your
dynamic framework from having to serve all these extra little
requests). Our control panel makes it easy for you to configure that.
* Use caching for expensive tasks: if parts of your pages are
expensive to build (for instance, they require multiple DB queries),
try to cache the result (either the HTML itself or just the result of
the DB queries) to avoid having to rebuild it every time."
--~--~---------~--~----~------------~-------~--~----~
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
-~----------~----~----~----~------~----~------~--~---
