PHP vs NodeJS Comparison and Benchmark

Almost every day there are some new technologies emerging, that are trying to change the web landscape. Server-side of the web development also is divided, there are long-standing heavy-weights such as Java, C, and Perl and newer, more web-focused languages like Ruby, Clojure and Go. But how to select a perfect solution for your project? We will compare two back-end technologies PHP vs NodeJS. We hope we won’t start a holy war.

First of all, let’s define PHP and Node.js. PHP is a server-side scripting language. It was created in 1994 by Rasmus Lerdorf in 1994 primarily for web development. Originally PHP stood for Personal Home Page, but now it stands for a recursive acronym – PHP: Hypertext Preprocessor.  

Usually, PHP is processed by an interpreter, powered by the Zend Engine, that is installed on web servers such as Apache and Nginx. Also PHP code can be embedded into HTML or HTML5 markup. This flexibility contributed to the popularity of the language, PHP is now used on more than 80% of web servers.

Node.js is an open-source, JavaScript run-time environment used to execute JavaScript code on the server-side. Node.js development process has changed the paradigm that JavaScript is used primarily on the client-side. That’s why Node.js has become one of the foundational elements of the “JavaScript everywhere” paradigm. Node.js was created by Ryan Dahl in 2009.

It is powered by Google’s V8 JS engine, that is the same engine that is used in Google Chrome web browser. This JS runtime environment doesn’t need a separate web server or other dependencies, there are built-in libraries that take care of that. Compared to PHP, Node.js is relatively young, however, it is already well recognized and used by giant companies like Microsoft, Yahoo, LinkedIn, and PayPal. For a clearer view, here is the PHP vs NodeJS comparison of the popularity indicators in the form of a table: 

Release date 08.06.1995 27.05.2009
Package’s repository (Dependency Manager) Composer NPM
Have LTS? + +
License (Free for commercial use) PHP License MIT License
Vacancies/ Developers ~100 000/4000000 60000/*
Packages  on packagist/ npm 152 453 ~450,000
Open-source projects 290,757 114,353
Questions on stackoverflow 1,112,866 187,917
GitHub stars 12 670 38 398
Contributors 485 1488
Most popular conferences of 2016 Laracon EU 2016
SymfonyCon Berlin 2016
Ski PHP Conference 2016
PHPBenelux Conference 2016
SunshinePHP 2016
The PHP UK Conference
Documentation ( (
Certification Zend
Symfony official certification
Node.js Certification Program

Benefits of PHP

Some developers say that PHP is much easier to use then Node.js. Their arguments are:

  • It’s easier to configure the development environment for PHP
  • Node.js requires more code
  • In order to code on Node.js, you have to understand callback functions and blockings
  • All internet hosting services support PHP
  • Supports more frameworks and CMS
  • Official code organization recommendations (PSR)
  • PHP has a larger library of instructions and frequently asked questions (there were plenty in 20 years)
  • The PHP developers community is a massive and diverse group of people, they are constantly re-visioning and updating libraries, frameworks and other PHP components

Get free estimation for your web app

Post your project or request a dedicated team - we'll quickly match you with the right experts.

Post project

You should consider using PHP when your project includes:

  • CMS technologies such as WordPress, Drupal, Joomla, etc, even if there is only a part of your project includes these technologies (for example blog, admin page, online store etc.)
  • If you are using a relational database – go with PHP.

To sum up the whole server side of this PHP vs NodeJS comparison, PHP supports following database management systems:

  • MySQL / MySQLi
  • SQLite
  • PostgreSQL
  • Oracle (OCI8)
  • Microsoft SQL Server
  • Sybase
  • ODBC
  • mSQL
  • IBM DB2
  • Cloudspace
  • Apache Derby
  • Informix
  • Ovrimos SQL
  • Lotus Notes
  • DB++
  • DBM
  • dBase
  • DBX
  • FrontBase
  • filePro
  • Ingres II
  • Firebird/InterBase
  • Paradox File Access
  • MaxDB
  • PDO

Benefits of Node.JS

One of the main advantages of NodeJS is the support of multithreading. While it is a necessity in browsers, it is not that much needed in web development process. A lot of developers choose Node.js over PHP. Here’s why:

  • Built-in server support
  • A single syntax for client and server side of the website. This improves the reusability of the code and makes the work of a full stack developer easier
  • Module caching – modules are downloaded and initialized when they are called for the first time, afterward they are constantly available
  • Stream module makes it easier to work with large files
  • Node has an almost identical syntax to JavaScript, thus it easy to pick-up and learn for JS developers.

Chrome V8 engine

As it was stated before, Node.js is powered by Chrome V8 engine. This engine is the source of many other benefits. You should consider using Node.JS when your project includes:

  • Streaming data transfer – traditional web stacks usually convert queries and corresponding HTTP to elementary events. However, they are data streams, and Node.js apps can take advantage of that. A great example of this kind of data stream is file processing during the download or data transfer between different layers.  
  • NodeJS supports real-time Web development – this allows to develop chats, betting apps, apps like Twitter, or interfaces for instant messaging with ease. But you have to be careful with that. Because the response time can vary, if the garbage collector interferes, he stops the execution of the program. So, don’t try to develop an app or a system with a guaranteed response time on NodeJS. Erlang is a way better choice for this job.
  • Software packages that include NodeJS, for example, MEAN (mongoDB, Express.js, Angular.js, Node.js)
  • Built-in expansion capabilities (cluster package)

Here is the PHP vs NodeJS comparison table of supported technologies:

CMS Magento, WordPress, Opencart, Drupal, Joomla, PrestaShop Apostrophe2, Ghost, KeystoneJS, enduro.js, Pencilblue
MVC frameworks Symfony, Laravel, Yii, Codeigniter, Zend, Phalcon, CackePHP Koa JS, Express JS, Sails JS
Realtime Ratchet, Wrench,, ws, Sockjs,
REST API RestClient, Guzzle, HTTPFUL Restify, Loopback
Scaffolding symfony+, laravel+ , yii+, CackePHP Yeoman
HTML templating Twig
Embedded js
Horizontal scaling implementation Elastic beanstalk, varnish Cluster mode, Amazon Elastic Beanstalk
Load balancer support + +
Queues + +
Multiple drivers support DB, storage + +
Full-text search + +
Profiling Xdebug, Blackfire, XHProf, XHGui Built in profiler
Caching Redis, Memcache Redis, Memcache
CI support Travis CI, Codeship Travis CI, Codeship
Cucumber (behat)


It is a good idea to choose a winner in PHP vs Node.js based on the features and benefits. However, it is always better to see how they are performing back to back, PHP vs NodeJS. We have created two different test cases and will run them on the same machine.

The test bench configuration:

  • VDS
  • CPU – 1 core, 2GHz
  • RAM – 1GB RAM
  • Storage – 10GB SSD
  • OS – Debian 8.6
  • PHP 7.0.22 FPM
  • Node.js 6.11.2

PHP vs NodeJS – First test

This test will show us how well PHP and Node.js are working with arrays,  string concatenation, network I/O, and arithmetics. Results for PHP:

php vs nodejs first test php
Results for Node JS:

php vs nodejs first test nodejs
As you can see PHP is faster than Node.js in:

  • Concatenation of strings
  • Filling array
  • Filling associative array
  • Reading the file
  • MySQL query

Node.js is faster than PHP only in adding numbers.

PHP vs NodeJS  – Second test

Now, we will test out how well Node.js and PHP are handling multi threaded tasks. We will throw at them 1000 queries in 1000 threads. Don’t look too hard into the source code, all configuration was done on the server side. Nginx 11.7 + PHP 7.1.1 FPM vs Node.js. Results for NodeJS:

php vs nodejs second test nodejs
Results for PHP:

php vs nodejs second test php

The second test has ended and the results are in favor of PHP, again. The numbers are:

  • PHP + Nginx – 32 ms
  • NodeJS – 200 ms

To put this numbers into a somewhat more acceptable form, PHP is capable to process 31,250 queries per second, Node.js, on the other hand, can deal with 5,000 queries per second.


PHP has won in almost every category of our PHP vs NodeJS comparison. PHP is more popular and easier to learn, yet it supports a significant amount of professional programming technologies and techniques. There are plenty of sources where you can get assistance and help and the deployment process is so much easier than Node.JS.

However, don’t discount Node.JS yet. Despite its steep learning curve, it has some really serious advantages. With the help of AJAX and HTML5 you can create very efficient apps and once the code is cached, the only thing that keeps transferring is data. In the end, there is no clear winner of PHP vs NodeJS. When you decide to create a new project, use the data presented in this article to pick what is best suited for your project and you.

Get free estimation for your web app

Post your project or request a dedicated team - we'll quickly match you with the right experts.

Post project

643 sharings



Totally wrong article, all the points are misleading and not compared properly. Cleary a biased opinion from the author who clearly favorites php


Content was good, but the tests were ingenuous.

Андрей Куфтачев

When I have the article I received two proposition make some project for me but the article show you aren’t professionals.

Node.js will be many times faster if you learn how to use it.


the nodejs codes aren’t using async. 🙁 not the right way to compare the speed.

Jim Kucera

Most small-medium size businesses won’t pay for NodeJS development work if they can get PHP developers for 1/2 the price and end up with ‘acceptable’ performance.


This design is wicked! You certainly know how to keep a reader entertained.
Between your wit and your videos, I was almost moved to start my own blog (well, almost…HaHa!) Excellent job.
I really loved what you had to say, and more than that, how you presented it.

link 188bet

Thanks for a marvelous posting! I definitely enjoyed reading
it, you may be a great author.I will always bookmark your
blog and may come back later on. I want to encourage that
you continue your great job, have a nice day!

Mikhail Orekhov

PHP 7 is considerably faster

Natalia N

Frankly speaking, any benchmark or a test is too synthetic. As Matthew reasonably mentioned above, the real projects have a great number of “details”. So benchmark results become inefficient. But we can analyze different use cases, e.g. streaming apps, CPU-intensive applications, multiple concurrent requests and so on. Just read at softmedialab dot com blog


this blog providing good information to learn NodeJS, Angular2/4, MongoDB, HTML, PHP, Hadoop… techiesguild dot com.

Karim mirak

they are right , and you used php+nginx (add more cache and perfromanence) ,you can use nginx with nodeJS then you will get a very diferente result, nodeJS have also others freamworks like AdonisJS same as laravel in php and more templates ,and NodeJS can hundle handred of thousends requestes without apache or nginx servers, and you dont need to configure your php.ini or simulars in nodeJS ,and you donr need to setup your server host for new modules ,and trust of that (nodeJS faster than php as expirence in both of them)


lol, the examples don’t show the best advantage of NodeJS, that is asynchronous. A nodeJS developer will use asynchronous iteration instead of synchronous iteration like that


    Asynchronous iteration of a blocking task? Sounds silly… Node is BLOCKING, but non-blocking IO.


      The tests on file streams, however, can be done async.

Mark Shapiro

did you run multiple node.js processes parallely with loadbalancer? or just 1 instance?

Peter Masterson

+1 For including Phalcon in the list of frameworks. While harder to use than a highly abstracted framework like Laravel, you can make absurdly fast APIs with Phalcon, and when you learn Phalcon, you are also learning PHP, whereas when one learns Laravel, he/she does exactly that, and a lot of the experience gained is non-transferrable.

Gentilhomme thomas

Your Node.JS test is synchronous… I rewrited (with my own JavaScript skills)

Node.js: concatenations of strings 1000000 times: 135.423867ms
Node.js: adding numbers 1000000 times: 9.382724ms
Node.js: filling of associative array 1000000 times: 33.333527ms
Node.js: filling of map 1000000 times: 776.473754ms
Node.js: reading the file 100 times: 35.38848ms

I dont have MySQL installed on my computer. But i can run the MySQL test in parrallel with the FS Test. We can achieve all tests in less than ~1seconde if we want ….

But the JavaScript VM test are not fair test (you have to test Node.JS event loop…)

    Gentilhomme thomas

    After few cycle of optimization of the JavaScript code :

    Node.js: concatenations of strings 1000000 times: 126.896592ms
    Node.js: adding numbers 1000000 times: 8.948083ms
    Node.js: filling of array 1000000 times: 13.301192ms
    Node.js: filling of hash 1000000 times: 49.676763ms
    Node.js: reading the file 100 times: 8.913275ms
    Total test execution time in MS: 207.735905ms

    The filling hash test was totally broked (the benchmark was more about string concatenation than Hash filling).

    Your PHP result for reading file is not possible without cache (so your php code only read the file one time whereas Node.JS read it 100 times). If we do the same on Node we get a close result of the PHP benchmark (but well, do it for real with 10,000 without cache and look who is winning … ).

    And Node still can handle the complete MySQL benchmark in parrallel.

    Same for the HTTP “hello world” benchmark (the php one is cached… Whereas the Node one is not). And please benchmark with autocannon (A node http server can handle around 30,000 hello world on a little configuration. Feel like your test is a fake and you writed the result yourself).

    And to make cached hello world on the Node.JS side please allocate a buffer to hello world and res.end(buf) without nothing else…


Matthew ftw! Came here to get solid information and Matthew’s post set me in the right direction. Nothing more than click bait.

Lars Schinkel

Also the network performance of PHP isn’t better in any case:

php on 7.2.1 / nginx 1.12.2

ab -k -c 100 -n 1000
Time taken for tests: 0.186 seconds
Requests per second: 5370.31

ab -k -c 100 -n 10000
Time taken for tests: 34.554 seconds
Requests per second: 289.40

node 9.4.0

ab -k -c 100 -n 1000
Time taken for tests: 0.247 seconds
Requests per second: 4044.65

ab -k -c 100 -n 10000
Time taken for tests: 1.098 seconds
Requests per second: 9105.96


The results in the article are quite true. I dont get the exact numbers but approximate. PHP definitely faster with this test. However like Matthew mentioned, PHP uses more resources in handling more requests than a NodeJs application would.

However, PHP is a more advanced language. You start to miss simple things like Late Static binding and Visibility when you work with NodeJS and Classes. But already pointed out is that NodeJs i.e Js is a newer server side language so I guess it will eventually start to have such features.

Matthew Kernes

The comparisons are pretty much garbage. Neither of these tests are real-world applicable tests. Constructing a single “Hello World” test, for example, is not exactly performing an apples-to-apples test.

If you wanted to perform the same test, you could just as easily configure nginx to spit out the result of “node test.js” with “console.log(‘hello world’);” as the only line of text in the code. In this case, it’s still possible that PHP will out-perform Node. Though, the test would actually be closer to accurate.

Put this into a real world scenario where you’re actually measuring performance of concurrent connections on sites with dynamic data and more than one page/module; that’s where things change. Node manages multiple concurrent connections better because it is not opening a new Node executable instance each time a request comes in, resulting in fewer PIDs and far less memory usage. PHP opens a new parsing instance with each request. If, in the real world, your webpage was actually “Hello world”, then PHP would be the right tool for the job.

But nobody’s website is actually “Hello world”. Websites are often intricate. And web apps are far more intricate. Managing hundreds (if not thousands) of concurrent connections requires a LOT more hardware with PHP than with Node because you run into limitations of memory. Even opening a PHP instance for “Hello World” for two connections is already double what you open for one. Rinse and repeat for hundreds of connections and you start to see a memory profile that looks like a tall hill.

On the other hand, do the same for Node, and the memory profile will remain mostly flat. Only a single instance must be open to manage multiple connections. (Though, many cluster node on machines with multiple CPU cores to exponentially increase connection handling.)

This is where real-world statistics comes into play:
If you have a website with low concurrent connections, PHP is an excellent solution because it’s quick to develop on. But if your site has lots of users constantly connected or making connections, Node.js is a far better solution, though may take a bit more scaffolding to get started.

I’m both a PHP and Node.js developer. I’ve much experience in both languages. I’ve been working in PHP since PHP 4, and I’ve been working with Node.js since 0.9. In both cases I’ve used them for their strengths in the right places. I can tell you with 100% certainty that this blog post is extremely biased (towards PHP) and doesn’t properly explain the strengths of Node.js. You might as well say, “Look how much better PHP is for websites than .” It also further misleads the reader that PHP can do things Node.js can’t. (i.e. “Here’s what DBs work with PHP”, no list for Node.js)

Furthermore, the conclusions of these tests don’t add up correctly. Supposedly, you’re transferring “Hello World” 50,000 times in each test. Yet, both tests have a different amount of transferred data in the tests. In one hand, you can say that PHP transferred more data faster. On the other hand, I can say PHP just cost me a lot more money to do the same thing I could have done in Node. So you have to explain the massive discrepancy in HTML transferred, at a minimum.

A proper test would include tests where Node.js would accel at as well, but it’s conveniently missing in this blog. Here’s a hint: Do a high concurrency test with PHP reading and writing to SQL and returning data. Then do the same with Node.js. Also, don’t use a 3rd party library like “mysql2” to connect to MySQL in Node.js. It’s significantly slower than the actual “mysql” library. (You could have found this out if you wanted to.)

BTW, I tested your script on my local, and first thing I noticed was that my numbers were totally different than yours. Obviously the (ms) would be different because we have different hardware/OS setups, but the numbers were sometimes flipped totally. For example, the “adding numbers 1000000 times” in your test takes about as much time as filling an array. On my rig, it takes 1/5th the amount of time as filling an array. There’s clearly a big discrepancy in either your rig’s hardware or your node environment optimization (which is why these results are far from scientific).

Finally, I recommend doing some research on what scientific tests look like. Performance benchmarking on your local computer as you’ve done is far from scientific and has no control cases. You provide very little information about the strengths of each server-side implementation, as well as providing no information about the system you tested on, let alone the OS and what type of installation and optimization for each server type you use for testing.

I recommend staying away from these types of hatch-job tests if you want to make have a credible name in the industry.

    Yana Gusti

    Hi Matthew,

    It is all relative, if you want to improve such comparison, you are welcome and we are ready to add your impact.

    Comapre PHP and Node.JS is same as comparing chocolate and orange. In any way, we are getting a lot of questions regarding backend, so decided to create such article.


    Wojtek Ślawski

    Then you need to do some research too. You can run php application as asynchronous with coroutine using php swoole. This will make applications as fast as nodejs with many concurrent requests or even more faster since whole core code is working in C.



dev py

Results and conclusions in this article are questionable.

Adam Wysocki

so making OnceBuilder CMS based on PHP was good idea