Allan.J at cobsen.dk
Wed Oct 25 13:54:34 CEST 2006
Den 24/10-2006, skrev "Dmitry Dulepov" <dmitry at typo3.org>:
>Allan Jacobsen wrote:
>> Whatever you do with apache each client will still spawn a server process (or
>> thread in case of apache2 thread mode)
>Not true. If you configure your server properly, proceses/threads will
>be there waiting for requests.
Yes offcause, but that is not the point.
Lets take a example from real life:
20 people want to see a page from our website, they point IE to an url
and it starts downloading the html(php) file. In that file there are
references to css and images, so shortly there are 5 connections from
each users IE to our server. That means that 100 apache connections are
made that each uses a min. of 1-2 Mbyte and a max of 20-40Mbyte. This
can be a big problem.
If we have squid in front of the webserver all 100 connections are
handled by 1 process, and it serves the images and css from cache most
of the time, so it is only 1/5 of the connections that reach apache, and
then the connection is local or by fast network, and not by adls or
modem, so the number of apache processes running will be very small.
At work we have 5000-10000 connections at peak hours, and I have never
seen more than 50 apaches running at the same time.
More information about the TYPO3-team-typo3org