Hi Woodsman
Caching, and lots of it, and DB clustering/replication are definitely the quickest fixes.
Caching (both on the server and the client side) are certainly looking good for my current project. I haven't used Cake's view caching yet, but am definitely going to look into it. I can well imagine the benefits
One minor point is to avoid using Cake's multi join SQL, which (I believe) can literally add thousands of queries when a single one would do.
I have spent some time optimising queries just with unbinding and have seen substantial improvements in DB performance (like half or one third of the processing time), so I can well believe the potential for improvement there.
And remember, hardware is less expensive than development time, so don't sacrifice code maintainability and clarity for tiny performance increases, as you'll pay a lot more in the long run.
This has become one of my main mantra. Yes, hardware is very cheap, especially compared to coding labor. And there is also nothing stopping you optimising code over time as well to take full advantage of that hardware.
Regards, Langdon --~--~---------~--~----~------------~-------~--~----~ 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 -~----------~----~----~----~------~----~------~--~---
