I would start a simple test with two different database. one very small with at least one but no more than 5 records per table.
Then do another test with a database with at least 1000 records in the tables that you would expect to grow. If your code is setup correctly with view pagination etc. the time between these two scenarios should change very little. If you see a huge delay difference with the 1000 record database, then you definitely have some bind or containable work to do. If both scenarios are slow, your going to have to look a little deeper at your code. As an example I had a wicked loop in my Auth and Menu system which generated 250+ querys for something that should have only been 13. Add to that a lazy find on my groups table which was bound to my Users via a HABTM mapping netting more than a few thousand users being pulled in for every cycle in this loop. I guess my point is cake is very flexible. Flexible enough to let you dig yourself a pretty deep hole. The DebugKit and FireCake has proven to be a priceless set of tools for debugging (mainly because their free) and they are very will put together, great examples of how to write plugins. I would add a couple log statments in your app_controller beforeFilter. spit out the controller and action that is being called. This will show you a nice trace of what your app is doing. I find this a good practice to run every once in a while. If you want a real test write down on paper what you think the trace of your app should look like for say logging in. Then log in and compare I'm going to bet there some stuff happening that you wouldn't expect. --~--~---------~--~----~------------~-------~--~----~ 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 -~----------~----~----~----~------~----~------~--~---
