Thanks for all the hints, they were very useful. I especially liked the web perf link Brad posted which quite honestly should be required reading for anyone in this group http://developer.yahoo.com/performance/rules.html
I was having some probs with prototype load time but bigger problems with initializing all the javascript. Due to the way the users want the app there can be many records (sometimes 50+) that use recursion=2 in the model, and there are (were!) at least 3 ajax->links per line item. The initialisation time of this was causing problems I think on the browser side. Ironically I had gone a bit beserk with ajax links thinking they would speed things up. I'd recommend looking at all the following for anyone thinking they have cake performance issues: - delve into mysql settings (a shared db host had no query caching switched on) (try http://www.ibm.com/developerworks/linux/library/l-tune-lamp-3.html ) - refactoring (forced by non related user feedback), to hugely reduce ajax-->links - compression of prototype - forcing client side caching of js (i.e. prototype) - thanks yahoo link - compression of css (asset_packager mentioned earlier in the thread is fantastic) - get using firefox and the firebug plugin to do profiling, it's rarely the php causing the prob Once these were implemented i no longer needed ajaxy links so much as the pages were rendering massively faster. Only after doing all the above is the DB query starting to come onto the radar for optimisation. HTH someone... Howard -- Howard Glynn - Edinburgh, UK [EMAIL PROTECTED] - email, google talk, facebook --~--~---------~--~----~------------~-------~--~----~ You received this message because you are subscribed to the Google Groups "Cake PHP" 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 -~----------~----~----~----~------~----~------~--~---
