Forget the architecture - I take significant exception to the basic arithmetic of these posts... Here's what they say > A simple LAMP stack server on an avera

Forget the architecture - I take significant exception to the basic arithmetic of these posts... Here's what they say > A simple LAMP stack server on an average 5.000 EUR server can – configured correctly – easily serve up to 6.000 requests simultaneously, probably even more if you use NGINX instead of Apache, because you do not hit the thread limit. > Now let us assume that a request takes 200ms to complete at the 99th percentile and that each user interacting with your offering sends a request every 10s in average. This means that you can serve up to 300.000 concurrent users, i.e., users that interact with your offering at the same time with a single LAMP stack node (6.000 * (10s / 200ms)). The server they reference has 20 cores. Let's say 40 threads. No LAMP (or probably any) stack is serving 6000 requests simultaneously on that, unless it's just a static html file (in which case they could serve considerably more). They're implying 6000/40=150 php workers per thread. That's insanity. The cache thrashing and context switching that would happen would make it so each page would take minutes to load.