3 ms·
> Code paths, auto-loaders, database connections, config files, etc. All that has to happen over and over for each request. So? If it takes < 1ms, what's the h
by bkanber 10y ago
> Code paths, auto-loaders, database connections, config files, etc. All that has to happen over and over for each request.
So? If it takes < 1ms, what's the harm? And opcode cache comes out of the box and most PHP DB drivers can use connection pooling.
We serve most of our requests in < 10ms, and we're not even on PHP7 yet.
- pharrington 10y agoIs machine computation mostly responsible for your revenue? If so, would it make more sense to measure web server responses in terms of cpu cycles and such instead of time?