@@hrabianero So that people would see that those frameworks make most things orders of magnitude slower. And don't get me started with ORMs and many-to-many relations...
@@DeskNook Can you try a new test with Laravel Octane and Swoole, this can give a really best performance, and test with pure php of course, this is really better than OPCache...
@@Trance_Code it's not better, it's also ridden with problems and the apparent speedup is negligible as you get better results with PHP-FPM without sideffects that come with Swoole and Octane. Octane is one big, big problem and shouldn't be used by serious apps.
Smaller frameworks has lower footprint, for the case, micro-frameworks are better considering OPCache On, between frameworks Symfony is faster and between micro-frameworks leaf & fatfree are in the same range however for micro-scale projects I prefer pure php
I really like Codeigniter a lot! But unfortunately, since version 4, it has been bloating and losing performance. In many benchmarks, it's shown to be lagging behind only Laravel :-(
I always knew Laravel is an overloaded mess. The developers became greedy and. integrated too much rubbish into it. Hit a bug and Laravel will send you to the loony bin, especially newbies. My advise: stay away from it.
As with all benchmarks, the relative performance depends heavily on the functionality you use in your benchmark code. If you are selecting a framework to do a "hello world" application, the best framework is the "none" framework. It is startlingly fast. It loads only 1 file. But if you're benchmark includes the sort of functionality that Frameworks provide, like ORM usage, html templates, data manipulation, the results will be different. Also, why would you ever run a complex framework with opcache off? Any benchmark with opcache off is irrelevant. That said, frameworks trend to preliad the entire framework and make zero effort to lazyload only the parts of the framework and application that are actually used. Doing this would be very beneficial to performance.
And this will scale with biger apps. As creator of PHP said all freimworks suck and as PHP progress this will be more and more true to the point of switching from framework to custom php solutions as it will yield much more stability, security and performace
Like & Subscribe
Like & Subscribe
Like & Subscribe
Long live pure PHP!
I would love to see similar test but with using pure php + pure sql vs frameworks and ORM
Lol, why?
@@hrabianero So that people would see that those frameworks make most things orders of magnitude slower.
And don't get me started with ORMs and many-to-many relations...
can you please benchmark fomo framework and laravel with octane ?
For a new framework 1:00 make sure to add it in the repo and ask for PR, asyn base stuff is out of the scope for the library
Nice one ! You did massive work !! Maybe you could also compare Async Frameworks ?
Thanks buddy, not sure about it actually its challenging to have fair benchmarks on PHP Async libs
PHP for Life! ❤❤❤
Thank you so much! This is very valuable information, keep doing this great work & benchmarks!
Why isn't Leaf more popular? It's one of the best PHP frameworks out there, and this benchmark proves it. It can even work with Swoole.
The competition between frameworks is high and speed is one of the factors however it wins in this comparison
@@DeskNook Can you try a new test with Laravel Octane and Swoole, this can give a really best performance, and test with pure php of course, this is really better than OPCache...
@@Trance_Code it's not better, it's also ridden with problems and the apparent speedup is negligible as you get better results with PHP-FPM without sideffects that come with Swoole and Octane. Octane is one big, big problem and shouldn't be used by serious apps.
So which one is fastest, and has smallest footprint? Pure php?
Smaller frameworks has lower footprint, for the case, micro-frameworks are better
considering OPCache On, between frameworks Symfony is faster and between micro-frameworks leaf & fatfree are in the same range however for micro-scale projects I prefer pure php
Let's test Nicotine Framework for PHP & MySQL!
Laravel! 😊😊😂😂😊😊
PS: Thank you for your work.
I really like Codeigniter a lot! But unfortunately, since version 4, it has been bloating and losing performance. In many benchmarks, it's shown to be lagging behind only Laravel :-(
please add mezzio php
please please please - add Codeigniter 3 on here as well - I think it will be much faster that CI4 - and many others
For Lavarel to be the most popular, it has some of the worst performance based on the graphs shown.
Laravel is so shitty nowadays....
missing to add KumbiaPHP :(
Test Trongate PHP. Thx.
Nice. Next time add Trongate framework. It’s mentioned ont the website that is fast.
phalcon, trongate?
I always knew Laravel is an overloaded mess. The developers became greedy and. integrated too much rubbish into it. Hit a bug and Laravel will send you to the loony bin, especially newbies. My advise: stay away from it.
Laravel has its pros and cons and one of the cons is the performance
@@DeskNook That is why o decided to create my own framework using pure php and basic libraries.
Yes we all should do that. Use Laravel only as template model. Only then innovation and intelligence begins.
As with all benchmarks, the relative performance depends heavily on the functionality you use in your benchmark code.
If you are selecting a framework to do a "hello world" application, the best framework is the "none" framework. It is startlingly fast. It loads only 1 file.
But if you're benchmark includes the sort of functionality that Frameworks provide, like ORM usage, html templates, data manipulation, the results will be different.
Also, why would you ever run a complex framework with opcache off? Any benchmark with opcache off is irrelevant.
That said, frameworks trend to preliad the entire framework and make zero effort to lazyload only the parts of the framework and application that are actually used. Doing this would be very beneficial to performance.
And this will scale with biger apps. As creator of PHP said all freimworks suck and as PHP progress this will be more and more true to the point of switching from framework to custom php solutions as it will yield much more stability, security and performace