Interesting function. A better test for you might be to put this call in the webroot/index.php (Sort of like the microtime guy). I say this because there's a lot of stuff that gets done in views (form helper, etc), which may cause blow ups.
I've never had a problem with memory before, but it seems that out of the box, Cake 1.2 was using about 6 MB just to display stuff through the pages controller. When I dumped a table less model on there (contact form) it went up to 7 MB. With that said, I loaded up a clean install of Wordpress and was running 5 MB out the gate. My main blog, uses 16 MB on the home page. As this is to say that, it would appear that your results aren't extraordinary and maybe bumping up the limit (if you can) would be the best way to go. Also, to answer my own question, there was no noticable difference while running in debug as apposed to production mode. -- Kevin Lloyd 3HN Designs http://www.3HNDesigns.com/ On Feb 4, 2008 2:25 PM, keymaster <[EMAIL PROTECTED]> wrote: > > Had to increase the php memory limit to 24M to get things humming > along nicely. > > That was probably the most reasonable approach given that cake 1.2 > with my models were sitting above 7M before my frst beforeFilter() was > even executed. > > > --~--~---------~--~----~------------~-------~--~----~ 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 -~----------~----~----~----~------~----~------~--~---
