3 ms·
Historical reasons...after nginx started blowing Apache's performance out of the water, Apache addressed some fundamental architectural issues and caught (mostl
by DantesRequiem 11y ago
Historical reasons...after nginx started blowing Apache's performance out of the water, Apache addressed some fundamental architectural issues and caught (mostly) up.
As an example, I would refer you to a discussion down this thread about Apache 1.x forking for concurrent connections.
- ryuuchin 11y agoAlso just for context remember that on linux forking and threads are basically the same thing so you can't just switch out one for the other and expect performance to change (it won't).
- WildUtah 11y ago"forking and threads are basically the same thing" It's nowhere near that simple. You can fork lightweight like threads or heavy. One of the terrible things about Apache performance was all the heavy forking on every single request for generated pages. That was back when it was really expensive.