I've had some issues too and will share some of my findings in hopes some more knowledgeable people will correct me where I'm wrong:
Is debug level set to 0? If there are lots of models loading (and not being cached) you'll hit some overhead. Probably not related to your specific problem, but I've noticed if you have a bunch of models loading with your request, there's 100-200ms of overhead per each model load. I've hit this problem with 20-30 models loading foreach of my ajax requests. If you look in your app\tmp\cache \models directory, you'll see these model cache files being recreated during each request. After spending days tracking this down, I figured that I'll just unbind all the models and bind just the needed ones. Uh-uh. Cake does all this *before* you get a chance at it (the best I could tell is that your first chance at anything is in Controller::beforeFilter(), which happens after all the model classes are contsructed). My conclusion (someone please correct me if I'm wrong here): if you have many relationships and don't use caching of your models, you'll have to avoid defining default bindings in your model files and manually bind models as needed per request. Another thing to note when debug level is not set to 0, your javascript files will be forced down with every page load. This is not an issue with ajax requests, though. Packaging/minifying your script and css is a good strategy to adopt to improve performance in that regards. --~--~---------~--~----~------------~-------~--~----~ You received this message because you are subscribed to the Google Groups "CakePHP" group. To post to this group, send email to cake-php@googlegroups.com 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 -~----------~----~----~----~------~----~------~--~---
