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 implementation it works for huge download services like RS very well, and THEY got massive traffic and heavy cpu usage for sure.
On Sep 21, 10:09 am, Bert Van den Brande <cyr...@gmail.com> wrote: > 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 web- and database servers is imho only a last resort, as > this will increase the overhead in maintenance, backup and deploying > significantly. > > Friendly greetings, > Bert > > On Mon, Sep 21, 2009 at 9:56 AM, marco.rizze...@gmail.com < > > marco.rizze...@gmail.com> wrote: > > > 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 suggestions on this forum about how scale > > CakePHP but I haven't found anything. > > Can someone help me about this with some example, link, tutorial etc.? > > Many Thanks --~--~---------~--~----~------------~-------~--~----~ 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 To unsubscribe from this group, send email to cake-php+unsubscr...@googlegroups.com For more options, visit this group at http://groups.google.com/group/cake-php?hl=en -~----------~----~----~----~------~----~------~--~---
