I was trying to do that, but loading one model loads lots of other
related models. That's why it take too long.
On 6 mar, 19:50, Miles J mileswjohn...@gmail.com wrote:
Well I use this technique, it only loads models that we need for that
current action. Cuts down the models tremendously.
Yes this is true of course, but it still cuts out unnecessary models
which help slightly. Im just hoping Cake can find a work around/fix to
that problem.
--~--~-~--~~~---~--~~
You received this message because you are subscribed to the Google Groups
CakePHP group.
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.
1000 rows is nothing, try 100,000 rows, then that would possibly
stress test the database and models.
--~--~-~--~~~---~--~~
You received this message because you are subscribed to the Google Groups
CakePHP group.
To post to this group, send email to
Profiling my applications give me some good insights about where our
application is having bottlenecks.
The slow methods within cake core are:
1. Loading models takes a lot of the time (85% of the total time),
specifically at Model::__createLink
2. FormHelper::select with large lists
Is there
Well I use this technique, it only loads models that we need for that
current action. Cuts down the models tremendously.
http://www.milesj.me/blog/read/16/loading-models-specific-to-certain-actions
--~--~-~--~~~---~--~~
You received this message because you are
Have you tried indexing your foreign keys?
I work on an app with a page that does about 100 minimum queries per
page load (it combines data from a lot of tables) and the query time
spent is only about 80ms.
On Mar 5, 6:10 am, Javier javier.cor...@gmail.com wrote:
Hello everyone,
I've read
Caching whole pages makes a difference:
http://book.cakephp.org/view/346/Caching-in-the-Controller
--~--~-~--~~~---~--~~
You received this message because you are subscribed to the Google Groups
CakePHP group.
To post to this group, send email to
Thx for the answers, here are some points:
1. We do have index on my DB (from primary keys and foreign keys
mainly), usually the DB access is really fast.
2. We aren't using the Containable behavior, but we make use of
bindModel and unBindModel to limit the queries produced
3. I just updated to
On Mar 5, 9:02 pm, Javier javier.cor...@gmail.com wrote:
Thx for the answers, here are some points:
1. We do have index on my DB (from primary keys and foreign keys
mainly), usually the DB access is really fast.
2. We aren't using the Containable behavior, but we make use of
bindModel and
Ill mention a few more things:
- Install the DebugKit. It has load timers for everything, the
controller, the views, etc so you can figure out whats taking the
longest.
- Look at all your queries and see what is taking the longest, and see
if you can lower what fields/relations are returned to
Hello everyone,
I've read some posts about cakephp performance posted here and we've
implemented some of the stuff discussed previously, but our
application still have a really slow response time (it feels really
really slow). We are using cake 1.2RC3 and we don't have an opcodes
cache (like APC
Hint: that RC in the version identifier (1.2RC3) stands for release
candidate. And the one that you have in particular is outdated by
several versions. We have a final release now, and several minor
releases that have come after it. That in itself is probably your
main issue.
On Mar 4, 3:10
Have you tried profiling your app to see where time is going?
Is the bottleneck on the server side?
Or is it the http requests due to your js, css, flash, images, and
other client side stuff?
If you come to this list with more specific information, you'll
probably get a better response.
Use containable instead of recursive. Thatll cut down a ton of
unnecessary queries.
My app currently has about 30 models and 40 database tables, all using
a ton of HABTM relations and it loads within 1 second.
--~--~-~--~~~---~--~~
You received this message
On Wed, Mar 4, 2009 at 4:17 PM, Miles J mileswjohn...@gmail.com wrote:
Use containable instead of recursive. Thatll cut down a ton of
unnecessary queries.
My app currently has about 30 models and 40 database tables, all using
a ton of HABTM relations and it loads within 1 second.
I'll
16 matches
Mail list logo
