3 ms·
>Your notion that forked = better is outdated. You're beating a strawman here. Nowhere did I make the claim that it was better. I even said multithreading is m
by bernawil 7y ago
>Your notion that forked = better is outdated.
You're beating a strawman here. Nowhere did I make the claim that it was better. I even said multithreading is more performant. The only claim I make is that immutable and shared nothing model of PHP servers makes horizontal scalling more straightforward.
>You're going to be using a thread pooled server anyway to handle requests
That doesn't take away the fact that n parallel requests will require n threads.
>And this doesn't even get into the more efficient compilation. PHP has no JIT yet. There's overhead for type inference. Etc etc
I don't make any claims here either. Of course Java is faster here. My point was specifically about which model of concurrency and paralellism is better for server IO.
- codesushi42 7y ago>That doesn't take away the fact that n parallel requests will require n threads. What's your point? In PHP's model, n requests will take n processes. There's no event loop in PHP. The forked model has nothing to do with making scaling horizontally more straightforward. In either scenario, you'll end up running a different process on another machine once you exhaust your resources.