I would like to know why we prefer to make web servers multi-threaded
instead of make it multi-process web servers ….
Is it because of legacy issues…..
I would like to hear practical reasons as well as theoretical reasons
Share
Sign Up to our social questions and Answers Engine to ask questions, answer people’s questions, and connect with other people.
Login to our social questions & Answers Engine to ask questions answer people’s questions & connect with other people.
Lost your password? Please enter your email address. You will receive a link and will create a new password via email.
Please briefly explain why you feel this question should be reported.
Please briefly explain why you feel this answer should be reported.
Please briefly explain why you feel this user should be reported.
I would like to know why we prefer to make web servers multi-threaded
instead of make it multi-process web servers ….
Is it because of legacy issues…..
I would like to hear practical reasons as well as theoretical reasons
On *nix, to start up a process you need duplicate all the resources of the parent process. All the parents file descriptors are dup’ed, for example, and a new memory space is created to contain the new process. When the process terminates everything has to be torn down.
A thread, on the other hand, is essentially just a stack. Very quick to start and stop.
Early web servers didn’t use threads for a simple reason: they weren’t implemented yet.