Refactoring Wordpress will make it even faster. Look at the difference between Drupal and Wordpress. It's amazing Wordpress is still used for big sites while a ton of recourses could be saved.
But great work on the PHP engine!
But great work on the PHP engine!
According to https://wiki.php.net/phpng, they benchmarked against Wordpress 3.6 (the current version is 3.9). I couldn't find anything about the Drupal benchmark, but it could be a simple "Hello world" for all we know.
Drupal's big two issues are bootstrapping drupal, because all those module hooks stack up quick, and the sometimes large amount of queries run to generate a page. Drupal 8 has gotten better about not loading half of the world when a blog post is loaded, but 7 is just a wall of functions.
I really don't understand people's aversion to database tables. I have a join, the world is ending! Pay attention to your indexes and 9 times out of 10 everything will be fine. For that 1 other time, there's Varnish.
As far as Wordpress, in my experience the number of db queries is really a bigger problem than the PHP processing. A factory-default install with no plugins runs 30 queries on every home page load. With a fancy theme and a few plugins it can be over 100 queries per page! A caching plugin is pretty much essential for any Wordpress site.
Most Wordpress sites use a caching plugin like WP Super Cache or Varnish-type setup if they get decent traffic though.
In my own benchmarks i've noticed all that class loading and instantiation slows things way down, even with an opcache. I find that a namespaced procedural / functional architecture performs much better, but no PHP framework works that way.
Also, CI out performs Symfony in the web framework benchmarks: http://www.techempower.com/benchmarks/. I certainly would never equate Symfony to "real speed".
So instead of just saying their Symfony benchmarks are bad, submit a pull request to fix whatever you think is wrong so they can get more accurate benchmarks next time.
Also their tests are run without caching for a reason. It's not a test of the language/framework if they just use whatever language to generate a static/cached file and serve it with nginx.
> Also their tests are run without caching for a reason. It's not a test of the language/framework if they just use whatever language to generate a static/cached file and serve it with nginx.
Haha lol, so the tests are explicitly meaningless. I guess I'm done here then.