[eluser]BeingDefined[/eluser]
Frogmoves, your response does make sense and got me thinking a bit. The way the database works right does infact give me a lot more control over how I want the caching want to be. I would go for the page caching but like you said it caches the whole view output but thats no good to because I have dynamic data that changes on every refresh. Since I just have about 10-15 pages getting hammered and causing like 70% of the 50% mysql cpu usage, I was thinking abt creating a cron script that would update the queries that don't change much every 30 or so minute. That way those queries are only hitting the mysql server every 30 minutes, instead of every page load. Before starting on this, the only question I have is how should I go about comparing the cached data and new updated query?
