Hi Jon
i didn't checked if cache is actually being written..
if it doesn't happens what could be the problem?

As far as the deployment, i know that a MBP doing nothing else is
a perfect server.. but in my opinion its 500 ms are still too much.
I have switched to cakephp after almost 1 year passed on building/
extending
my own framework, because i found it very easy and well done
mine had many design problems a probably many efficiency problems..
but it only used to take 150 ms on the same MBP ..70% off of the time
cakephp takes..

Anyway the html->link fact is worrying me, maybe i should convert all
those calls to direct URLs ..or at least do not use the array Url
format
('controller'=>'posts','action'=>'view',34) but /posts/view/34 .

thanks,
   Andrea

On Dec 18, 3:30 pm, "Jon Bennett" <[email protected]> wrote:
> Hi Kappa,
>
> >  I also enabled caching on each requestAction (1 day) but nothing
> >  changed;
>
> are you sure the cache's are being written? look in /tmp/cache/views
> for $this->element caches, and /tmp/cache/models for things written in
> the model with Cache::write
>
> >  the overall database time is quite small (40msec) but the whole page
> >  loading
> >  takes about 500msec on my own MacBook Pro .. but 4-5 seconds on the
> >  server
> >  that hosts the site ..with 1 connection only.
>
> A MBP doing nothing else is a pretty beefy server, so to give a better
> idea of the comparison, what hardware are you deploying on? Can you
> increase the memory allocated to php via php.ini or .htaccess? Most of
> my projects have a 64mb+ limit set.
>
> hth
>
> jon
>
> --
>
> jon bennett
> w:http://www.jben.net/
> iChat (AIM): jbendotnet Skype: jon-bennett
--~--~---------~--~----~------------~-------~--~----~
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
-~----------~----~----~----~------~----~------~--~---

Reply via email to