News for hackers. Stuff that matters.
Re:PH7 – An Embedded Implementation of PHP (C Library) by webjprgm on Wednesday February 19, 2014 @01:45PM (#7265313)
I usually see arguments like this about language performance, but do people also argue about the difference from having a server process launch, configure itself, and stay open handling requests, like Ruby or Node.js, versus re-running initialization on each request like PHP?

A lot of that initialization code is hooking together objects, reading misc config flags, and setting up request routing. But what about ORM? Ruby's ActiveRecord has to query the database for a schema, right? In PHP that query would be done every request rather than just once when the server restarts.

Could this architecture issue have a larger performance impact than the minor differences in Python / PHP / Javascript / Ruby performance?

(There were also plenty of discussions about event-based programming versus blocking + multi-threading back when Node was becoming popular. That is another example of architecture being more important than execution speed.)

There are no comments on this comment yet.