I've not found MVC frameworks to scale well regardless of the one you pick. Knowing how many records you've got isn't all that helpful either because it's how you interact with them that affects performance.
CakePHP is as good as any MVC out there though if you're set on using one. As others have said there are examples of big sites using it. Addons from Mozilla is about the biggest though and they likely have at least some C on the serverside doing things as well to support the heavy lifting. There aren't any great benchmarks out there for MVC frameworks since each offer so much variety in terms of core components, ORM layers, etc. The bottom line is that if you've got an incredibly high volume site, and you're regularly managing those 2 million records, you're better off writing some kind of C supported PHP you roll on your own. Your code is going to get slow with every bundled package that needs to load or ORM feature you don't necessarily need. With those kinds of records you're trusting that the ORM layer is doing things like sorting results in the most efficient way. On Jun 26, 3:32 am, "Techinfocomp.com" <[email protected]> wrote: > can we make a big website in cakePHP like aprox 2,00,000 records > website in cakePHP. > > and website can open withought taking any time if db will grow in > size ? > > is cakePHP is best solution for very Large Website ? --~--~---------~--~----~------------~-------~--~----~ 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 -~----------~----~----~----~------~----~------~--~---
