http://www.mysqlperformanceblog.com/
I hope you have seen this blog? They have had a number of post lately
about indexes and always post about optimization in one way or the
other (funny enough).
If you have added indexes which did not improve much you may be
defining them wrong for the query
http://www.mysqlperformanceblog.com/
very interesting. From reading
http://www.mysqlperformanceblog.com/2009/09/19/multi-column-indexes-vs-index-merge/
it would appear that for join tables, indexes with both keys would be
best, rather than a single key per column.
Good tip for the day that :)
Hi
I have developed my web application with CakePHP.
For the moment I use one Apache server and one MySql server.
Now I have noted that my application is getting slow because the
numbers of users is increasing.
So I have decided that is the time to scale my architecture.
I have tried to find some
hi marco,
It's early, not had coffee yet - and I missed this crucial comment:
For the moment I use one Apache server and one MySql server.
As you've already separated mysql and apache, how about adding another
apache server, using memcached to share sessions between the 2, and
something at
First you need to find out why your application is getting slower, this can
be a database issue or a PHP scripting issue ... or a combination of both :)
Lots of caching options are provided by Cake, those should get you a long
way in improving the performance of your site.
Scaling to multiple
Hi marco,
I have developed my web application with CakePHP.
For the moment I use one Apache server and one MySql server.
Now I have noted that my application is getting slow because the
numbers of users is increasing.
So I have decided that is the time to scale my architecture.
I have
In general, besides the noted tips:
- Take a look at lazyloader/lazyloading models
- Do not use Model-recursive 0, use Containable. You might look
into Translateable as well
- DEBUG sql outputs, see where the heavy load is happening.
On Sep 21, 9:56 am, marco.rizze...@gmail.com
While not having much of experience with scaling, scaling the DB by
using InnoDB + UUIDs and Replication should not be a huge Problem.
What I would do for the application is adding a proxy that redirects
like www1.domain.tld www2.domain.tld and so on, though I have no
knowledge about
My big problem is that I have some tables there are very and very
huge.
I have add indexes but the situation is not improved much
Is someone can suggest me how can I manage very large table with mysql
and CakePHP without scaling mysql?
On 21 Set, 17:25, j0n4s.h4rtm...@googlemail.com
Well how big is your table? I have tables with over 200,000+ rows and
it works just fine.
--~--~-~--~~~---~--~~
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
i was successfully able to handle tables with more than 200 records
yes, above 2 million records! with CakePHP and with a very acceptable
performance and speed, the first thing that you should be thinking of is
sharding the database into smaller chunks DBs, second thing is enabling
memcached
My table is about 30 records with only 5 fields
It's a jointable of a HABTM relation.
But I use this table in some INNER JOIN in some queries that are very
slowly.
I use memcache.
In these cases what is the best practise to consider?
On 21 Set, 20:20, Ma'moon phpir...@gmail.com wrote:
i was
12 matches
Mail list logo
