You'll get to market faster, but you'll also be planning a rewrite or migration sooner should you enjoy some degree of success.
You'll get to market faster, but you'll also be planning a rewrite or migration sooner should you enjoy some degree of success.
In almost all cases, the benchmark was done with no caching. I don't know who launches web apps with no caching, but they shouldn't be doing benchmarks.
I don't concede that Cake is slow for any meaningful definition, but as a matter of point - I'll trade faster developers for a couple CPU cycles any day of the week.
Most frameworks are bloated (not setup to REALLY scale) out of the gate.
CakePHP is very flexible, and if used correctly can scale for 99% of workloads. Especially if you leverage some of the php5 only nuances (cake 1.3 has been developed to support php4 and php5).
CakePlate can steer you in the right direction - but is not an end all. It helps turn your idea into reality quicker. If your idea twitter scales, then you have cash to throw at the (good) problem.
If you give Cake an honest shot, I'm confident you will like it.
this and similar reports from others are the reason i don't use cake, though, and it seems like it would be in their best interest to get some newer information out there. (i made my choices years ago though)
Take with a grain of salt.
EDIT: yeah, pretty sure the original Yii benchmark is dated as the graph has older versions while the phpmark repo has slighlty newer ones ( http://code.google.com/p/phpmark/source/browse/#svn/trunk )
They've rebuilt much of the base code on top of PHP 5 natively now instead of being built on PHP 4 with hacks to make it also work with 5.
Although it is still in development, it has been said that it is stable.