3 ms·
see: drupal. having to execute the whole application from the entry point on every page hit is just awful. APC will only save you the loading from the disk and
by AdrianRossouw 13y ago
see: drupal.
having to execute the whole application from the entry point on every page hit is just awful. APC will only save you the loading from the disk and compiling part, not the whole execution chain.
with node and others the application is just sitting there, listening to a port, and fires the right callbacks when a request comes in. the application startup cost is paid once. not on every request.
there are people who have tried to reproduce it in php by having php running and serving multiple requests in a similar manner. This is really treacherous since php didn't even pretend to free memory under any circumstances ever, until about php 5.3.
since moving over to writing servers, i just feel that the php model of executing the script when a url is hit is just fundamentally wrong.
- swalkergibson 13y agoDrupal lives in its own separate category somewhere near Mars. Just because Drupal is slow does not mean that PHP itself is the reason why. > APC will only save you the loading from the disk and compiling part Is that not the slowest part? According to the benchmarks here, http://www.techempower.com/benchmarks/#section=data-r7&hw=i7&test=json http://www.techempower.com/benchmarks/#section=data-r7&hw=i7..., PHP is only really slower than Node in serving up a plaintext response and a json serialization (although, it is only about a 5% difference in responses/sec between the two).