hi Alex, >> In terms of profiling - it sounds like its the DB that's being >> sluggish, how many hits are you getting? on what spec server? if you >> have access you could run >> http://www.webdevelopmentstuff.com/123/optimizing-mysql-performance-tuning-script.html >> to try and optimise your mysql server. > > Yeah I think I'm just too lazy when it comes to indexes. Definitely > using Containable, but should probably be making better use of > caching.
Indexes make a huge difference, as does using the right column types. Containable is great, but you still need to analyse what's being retrieved and adjust. As little as possible generally! > Whilst there is the core cache library which is great, do you use any > kind of component in front of this to abstract it? Or is it a case of > manually checking whether the cached element exists in your controller > action and then if not fetching from the DB? I have a custom solution based around Mile J's http://www.milesj.me/blog/read/34/Cacheing-Each-Query-Individually. It's pretty easy to cache stuff though, it's knowing when to clear them out that's the tricky bit. Cheers, J -- jon bennett - www.jben.net - blog.jben.net Check out the new CakePHP Questions site http://cakeqs.org and help others with their CakePHP related questions. You received this message because you are subscribed to the Google Groups "CakePHP" 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/cake-php?hl=en
