Tip of the day: "Читайте спецификации"
FastCGI спецификация (1996)
Java Servlet Programming (2001):
"This eliminates the need to create a new process for each request. Although FastCGI is a step in the right direction, it still has a problem with process proliferation: there is at least one process for each FastCGI program. If a FastCGI program is to handle concurrent requests, it needs a pool of processes, one per request. Considering that each process may be executing a Perl interpreter, this approach does not scale as well as you might hope."
Либо авторы нихрена в программировании не понимают (что очевидно не так) либо читают очень медленно.
Java Servlet Programming (2001):
"This eliminates the need to create a new process for each request. Although FastCGI is a step in the right direction, it still has a problem with process proliferation: there is at least one process for each FastCGI program. If a FastCGI program is to handle concurrent requests, it needs a pool of processes, one per request. Considering that each process may be executing a Perl interpreter, this approach does not scale as well as you might hope."
Либо авторы нихрена в программировании не понимают (что очевидно не так) либо читают очень медленно.