If you use mod_perl and dbi you should be sweet if you have enuff mem and tune your http server accordingly.</p.
While I agree the terms 'heavy load' and 'too much traffic' are subjective or at least unqualified, you will be able to test and monitor your project to provide useful benchmarks to go by.
In terms of dynamic content caching perhaps you could use a cookie to give you the last bit of content retrieved, then use the cookie value to determine if there is new content to get. If the content hasnt changed, send back the cached page, otherwise, replace the cached page and send it back.
If your application has a high transaction rate, perhaps you could use a combination of timestamp/token to prevent you flushing the cache all the time (and making it useless).
Perhaps some lessons could be gained by checking out how the chatterbox works. It is both dynamic, and has a relatively high transaction rate.
In reply to Re: Opening too many files?
by Ryszard
in thread Opening too many files?
by Chady
For: | Use: | ||
& | & | ||
< | < | ||
> | > | ||
[ | [ | ||
] | ] |