Always remember to check http codes in cats :

Basically,youmadesomuchexecutiontotheapachethatsomepartsofitsaid"goodbye, cruel life". One of these parts was the logger / appender, which did not support the excess of requests; Apache was so crowded that it could not even respond in a timely manner to a request, he envisioned the result of all these repetitions.

I've been looking here as apache handles the requests. I thought that for each request it would open a new thread, but I did not find a quick search something confirming my suspicions ... However, I found an English reference on the life cycle of an HTTP request in apache . Maybe it's worth a read.

EDIT

I found some reference to apache and threads in a International StackOverflow quest . Basically, every request that apache can handle will create a new program context to serve it. This can generate a processing bottleneck (each processing core can only serve a single context in that sense) as well as a bottleneck in memory (each context requires a bit of memory to run; need 1KB to run, then 1 million requests will create 1 million different contexts, so in this scenario, it would need at least 1GB of initial context information only; EMPHASIS: THIS IS AN EXAMPLE WITH INVENTED DATA WITHOUT BASED ON REALITY, USED ONLY TO EXPLAIN THE WEIGHT OF THOSE MANY THREADS ).

To avoid this kind of vulnerability, node.js (a purely JavaScript server) uses a limited number of threads to requisitions, usually just one.

In conclusion, it would be nice to have a graph analyzing server performance by showing how much CPU and memory is being used.