2008/9/4 Michel Morelli <[EMAIL PROTECTED]>: > There are no rules. Depends on your data.
Agreed. We tend to examine our SQL queries (thats all we cache currently) and work backwards from there. We have the situation as we aggregate result data nightly into different tables to make SQL selects simple for viewing historical data. Historical data as it will never change can be cached forever if we wanted but we leave it at 24hr. However slower SQL tends to get cached as long as possible. In our secnario, slow SQL indicates to us that the DB is changing quickly (i.e. its data that reflects today) so we have to provide a trade off. Not killing our DB with many queries but providing uptodate information. It can be hit and miss (pardon the pun) for a while till you see how busy your site gets too and what else is running on the servers. That been said we had a site TC'd recently and just ran a 5min cache for all SQL no problems. My 2c AJ
