dcsimg

Ace's Hardware: Building a Better Webserver in the 21st Century

By ServerWatch Staff (Send Email)
Posted Nov 30, 2001


This article talks about the hardware and software changes when upgrading a webserver. They end up using an alternative to Apache. Share your comments in the talkbacks below.

"Our old web application was written in PHP and ran on Apache, a "pre-fork" multiprocess HTTP server. Apache works by starting a parent process which then forks several child processes to listen and wait for HTTP connections. Since, each of these child processes serves one HTTP request at a time, Apache creates a pool of processes to handle connections in a timely fashion. Our old web application was written in PHP and ran on Apache, a pre-fork multiprocess HTTP server. Apache works by starting a parent process which then forks several child processes to listen and wait for HTTP connections. Since, each of these child processes serves one HTTP request at a time, Apache creates a pool of processes to handle connections in a timely fashion. This article talks about the hardware and software changes when upgrading a webserver. They end up using an alternative to Apache.

The disadvantage of this approach is that it can result in a great deal of overhead due to the 1:1 ratio between processes and requests. This can be particularly true in the case of HTTP keepalives, a feature designed to speed up web serving by handling multiple sequential requests from a client on the same connection, saving the time of having to build up a new connection for each request. ..."

Page 1 of 1


Comment and Contribute

Your name/nickname

Your email

(Maximum characters: 1200). You have characters left.


 

 


Thanks for your registration, follow us on our social networks to keep up-to-date