Comments on: PHP Frameworks Explained http://www.mitchitized.com/nerdy-stuff/php-frameworks-explained/ the online home for mitch pirtle Fri, 30 Jul 2010 12:03:04 +0000 hourly 1 http://wordpress.org/?v=3.0.1 By: Oleg Baranovskyhttp://www.mitchitized.com/nerdy-stuff/php-frameworks-explained/#comment-756 Oleg Baranovsky Tue, 23 Feb 2010 00:30:59 +0000 http://www.mitchitized.com/?p=56#comment-756 @Brian Migliorisi: CakePHP was designed for older PHP4 and tried to emulate a lot of OO stuff that was not existent in PHP at the time. This obviously comes at a heavy price -- we were doing some profiling there and it runs like 250 KB in the memory even before it starts doing anything useful. It is a great framework to bake something really fast, but do not expect it to scale. The original developers of Cake actually started the new project called Lithium (http://lithify.me/), which is a complete rework for PHP 5.3 and higher. It uses the new advanced features now available in PHP and should be much faster and more scalable.The newer frameworks, like Yii and Kohana are created for PHP5 and obviously are much optimized (and therefore fast and scalable) as compared to Cake. @Brian Migliorisi: CakePHP was designed for older PHP4 and tried to emulate a lot of OO stuff that was not existent in PHP at the time. This obviously comes at a heavy price — we were doing some profiling there and it runs like 250 KB in the memory even before it starts doing anything useful. It is a great framework to bake something really fast, but do not expect it to scale. The original developers of Cake actually started the new project called Lithium (http://lithify.me/), which is a complete rework for PHP 5.3 and higher. It uses the new advanced features now available in PHP and should be much faster and more scalable.

The newer frameworks, like Yii and Kohana are created for PHP5 and obviously are much optimized (and therefore fast and scalable) as compared to Cake.

]]> By: janehttp://www.mitchitized.com/nerdy-stuff/php-frameworks-explained/#comment-140 jane Thu, 24 Sep 2009 01:43:01 +0000 http://www.mitchitized.com/?p=56#comment-140 Interesting! Always looking for useful SEO tips. Interesting! Always looking for useful SEO tips.

]]> By: Twitter Trackbacks for PHP Frameworks Explained « mitchitized [mitchitized.com] on Topsy.comhttp://www.mitchitized.com/nerdy-stuff/php-frameworks-explained/#comment-40 Twitter Trackbacks for PHP Frameworks Explained « mitchitized [mitchitized.com] on Topsy.com Wed, 26 Aug 2009 18:11:27 +0000 http://www.mitchitized.com/?p=56#comment-40 [...] link is being shared on Twitter right now. @mitchitized, an influential author, said Going to bed now, [...] [...] link is being shared on Twitter right now. @mitchitized, an influential author, said Going to bed now, [...]

]]> By: Bryan Migliorisihttp://www.mitchitized.com/nerdy-stuff/php-frameworks-explained/#comment-37 Bryan Migliorisi Wed, 26 Aug 2009 14:22:01 +0000 http://www.mitchitized.com/?p=56#comment-37 I tried CakePHP, Symphony, CodeIgniter and finally Yii. I did some simple testing on each of them - creating a single controller and view, but no model because I didn't want data access to skew my results.I created a simple test where the model set a bunch of data and the view displayed the data. I used the template system in each framework. Aside from data access, it illustrated a typical page request lifecycle.After running some simple benchmarking using apache bench (ab), it was clear that CakePHP was the slowest of all with an average of around 18 requests/second. I was very surprised to see that, since I hear so many great things about Cake. Yii rolled in at around 120 requests/second. An incredible difference which can be attributed to Yii's lazyloading technique for all classes. I *think* CakePHP 3 is going to use the same technique for loading modules and classes to help boost its performance. I tried CakePHP, Symphony, CodeIgniter and finally Yii. I did some simple testing on each of them – creating a single controller and view, but no model because I didn’t want data access to skew my results.

I created a simple test where the model set a bunch of data and the view displayed the data. I used the template system in each framework. Aside from data access, it illustrated a typical page request lifecycle.

After running some simple benchmarking using apache bench (ab), it was clear that CakePHP was the slowest of all with an average of around 18 requests/second. I was very surprised to see that, since I hear so many great things about Cake. Yii rolled in at around 120 requests/second. An incredible difference which can be attributed to Yii’s lazyloading technique for all classes. I *think* CakePHP 3 is going to use the same technique for loading modules and classes to help boost its performance.

]]> By: mitchyhttp://www.mitchitized.com/nerdy-stuff/php-frameworks-explained/#comment-36 mitchy Wed, 26 Aug 2009 12:48:21 +0000 http://www.mitchitized.com/?p=56#comment-36 You're the second person that recommended that framework, I have to check it out. You’re the second person that recommended that framework, I have to check it out.

]]> By: adwinhttp://www.mitchitized.com/nerdy-stuff/php-frameworks-explained/#comment-35 adwin Wed, 26 Aug 2009 09:28:56 +0000 http://www.mitchitized.com/?p=56#comment-35 you forgot to mention Yii Framework from the author of Prado Framework.http://www.yiiframework.com/it looks like Ruby on Rails and has ActiveRecord. you forgot to mention Yii Framework from the author of Prado Framework.

http://www.yiiframework.com/

it looks like Ruby on Rails and has ActiveRecord.

]]>