On 28 Mag, 19:33, Joel Perras <[EMAIL PROTECTED]> wrote:
> On May 28, 12:58 pm, "[EMAIL PROTECTED]"
>
> <[EMAIL PROTECTED]> wrote:
> > With debug=2 the queries are exaclty equal except for the DESCRIBE
> > operation on the joinTable.
>
> As I stated previously, when debug = 0 these queries are cached.
>
> > Perhaps it'is a my feeling.
> > Exist a instrument for evalute the time loading of a scripts?
>
> A quick and dirty way of benchmarking page rendering time would be to
> put a call to microtime() in app_controller.php in both the
> beforeRender() and afterFilter() methods, and echo/log the time
> difference between the two.
>
I use this method and I test this case
In cake 1.2 : a controller -action with one read operation ;
controller uses one model.
debug: 2
In cake 1.1 : a controller -action with one read operation ;
controller uses teen model.
debug: 2
Using microtime in app_controller.php I get that:
Cake1.2 is always over 100ms
Cake 1.1 is always over 60ms
The incredible thing is that from debug it seems that the controller-
action in Cake 1.1 makes more queries (DESCRIBE query) because it has
to load more models that cake 1.2
> > Is it possible to use eAccelarator with Cake 1.2?
>
> Cake actually uses Memcache (a PHP wrapper for memcached) for
> caching. Sadly there isn't anything in book.cakephp.org describing
> this (yet), but a few well placed google queries and a quick search of
> this group should give you an idea of how things work. I've never
> used eAccelerator, but I've heard of other people who have used it in
> conjunction with Cake.
>
> -Joel.
--~--~---------~--~----~------------~-------~--~----~
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
-~----------~----~----~----~------~----~------~--~---
