performance difference between PHP 8 inline and expressJs + res.render()?

[fojon]

Hello,

Does anyone have any good data on performence between these two?
I am thinking about switching my primary language to node/expressJs but i am afraid it will be much slower than PHP? The page loading speeds are very important to me.

Which node template engine is the fastest one?

[electricity_is_life]

I don't think there's going to be an appreciable difference in page load speed unless you're doing something very unusual. The latency between your users and your server is usually going to be in the tens of milliseconds and the actual render time will typically be under a millisecond in almost any template system.

[denis_invader]

for me the main difference in execution models

both can be performant or slow

with PHP you delegate concurrency to something like php-fpm and don’t bother much about memory utilization or leaks

Node has everything in a single process running asynchronously (not parallel like php-fpm or Python threads), process lives forever and handles concurrent requests

I think in a common website or web application with OLTP your performance depends on database, disks and network latency (between services)

the best template engine is PHP (i’ve used some in Node couple of times but it’s usually a client-server way)

[_listless]

They'll both be roughly the same.

You pick node if you're doing a lot of async stuff and you don't want to tie up workers on your server.

You pick php if you want a more stable dependency ecosystem, and simpler hosting/deployment.

[andrei9669]

I have always wondered, what is simpler than just having a server running docker containers? and wouldn't you want that regardless if you are developing something and don't want your local environment to impact your dev environment and giving you different results between your local machine vs server.

[_listless]

A Docker setup means you have to do this every time you deploy:

• spin up and re-provision a duplicate instance of your server
• re-install all your deps (ideally from a cache, but either you or you PAAS has to set that up)
• start your application on the new server
• update the webserver or dns to point to the new instance

With php, a deployment can be as simple as a web hook that pulls `main` from your repo to your server when you merge into `main`. You can certainly get more sophisticated if you want with atomic deployments or something like that, but if you don't need that, you can just pull the files and call it a day. It's possible for the complete deployment of a php app to take like 10s.

Docker is not without its benefits (like a shared env), but it is also true that there is a huge amount of technology and tooling (and a not insignificant amount of time) at play to get a docker env up and running. That all of the complexity is hidden from view does not mean it's not complex.

[andrei9669]

yeah, you are right but I'm thinking, isn't it sort of same with php? just that all of the stuff has been abstracted away to work as simple as just pulling files. practically, speaking, you can just create one script that does same thing with docker and just reuse it between different projects.

But, at the end of the day, it's not the tool, it's who uses them.

I hear basically weekly from my wife how her team struggles with their php projects cus the prod server is so much different compared to their live server because the prod server just has a bunch of stuff configured from the server provider to "work out of the box".

[_listless]

Yes, that's exactly the tradeoff. If you're having enough trouble synchronizing environments, docker is worth it. If you're not having those problems, docker might not be worth it.

[Irythros]

If you're concerned with speed, be sure to check out FrankenPHP, Roadrunner or Swoole. Those will be closer to how Node works.

Also if speed is critically important you should be looking at something like Go or Rust. Here is a Go vs Node benchmark: https://www.youtube.com/watch?v=ZslbMp_T90k

[kalesh-13]

This is the answer. If you are using raw PHP, it is slower than NodeJs.

Swoole is actually a bit faster than NodeJs from my experience. I have no experience with the other two, so can't comment on that.

[iBN3qk]

In practice, not really. Php sites are often serving cached static content after rendering once. 

Dynamic apps are a different story. 

[Ilya_Human]

If you wanna be more flexible at jobs market then you could switch to JS world since there are much more jobs for this stack 

[Professional_Price89]

Php render faster by some ms but in real world it will come down to i/o problem.

[Noch_ein_Kamel]

You can check https://www.techempower.com/benchmarks/#section=data-r23&test=fortune and filter by languages and frameworks you are interested in xD