You are viewing a plain text version of this content. The canonical link for it is here.
Posted to users@httpd.apache.org by Arianna Manlio <ar...@yahoo.com> on 2012/03/08 15:35:01 UTC
[users@httpd] "client" or "request" meaning
Hi,
sorry for previous message.
I'm trying to fully understand the meaning of "client" or "request" concepts in Apache.
For example:
http://httpd.apache.org/docs/2.2/mod/mpm_common.html#maxclients
Description:Maximum number of connections that will be processed
simultaneously
...
The MaxClients directive sets the limit on the number of simultaneous requests that will be served.
So, what is a "connection"?
If I connect to my home webmail, I see several connection, even if I the only user.
This means that 5 or 6 "clients" are already reserved?
Thankyou very much.
Re: [users@httpd] "client" or "request" meaning
Posted by Nick Kew <ni...@webthing.com>.
On Thu, 8 Mar 2012 14:35:01 +0000 (GMT)
Arianna Manlio <ar...@yahoo.com> wrote:
> So, what is a "connection"?
> If I connect to my home webmail, I see several connection, even if I the only user.
> This means that 5 or 6 "clients" are already reserved?
Most of those connections are probably just in keepalive state
when you see them (i.e. finished, but not yet closed).
If they're a problem, reduce your keepalive timeout.
But 5 or 6 connections won't put a noticeable load on your
server (unless perhaps it's 20-year-old hardware).
--
Nick Kew
---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@httpd.apache.org
For additional commands, e-mail: users-help@httpd.apache.org
Re: [users@httpd] "client" or "request" meaning
Posted by Daniel <da...@gmail.com>.
1 visitor = 1 client, but 1 visitor =/= 1 connection and 1 client =/= 1
connection
On Thu, Mar 8, 2012 at 12:31 PM, Arianna Manlio <ar...@yahoo.com>wrote:
> Hi Simone,
> so, it's wrong to think that 1 visitor = 1 client, right?
>
> ------------------------------
> *Da:* Simone Caruso <in...@simonecaruso.com>
> *A:* users@httpd.apache.org
> *Cc:* Arianna Manlio <ar...@yahoo.com>
> *Inviato:* Giovedì 8 Marzo 2012 16:49
> *Oggetto:* Re: [users@httpd] "client" or "request" meaning
>
> > So, what is a "connection"?
> A connection is a single I/O channel between hosts (TCP,UDP, UNIX SOCKETS)
>
> > If I connect to my home webmail, I see several connection, even if I the
> only user.
> > This means that 5 or 6 "clients" are already reserved?
> >
> When you connect to a website u use about 4/8 connections (images, css,
> ajax).
> The number of connection depend on browser type, server configuration and
> average load, network latency.
>
> --
> Simone Caruso
> IT Consultant
> +39 349 65 90 805
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: users-unsubscribe@httpd.apache.org
> For additional commands, e-mail: users-help@httpd.apache.org
>
>
>
>
Re: [users@httpd] "client" or "request" meaning
Posted by Arianna Manlio <ar...@yahoo.com>.
Hi Simone,
so, it's wrong to think that 1 visitor = 1 client, right?
________________________________
Da: Simone Caruso <in...@simonecaruso.com>
A: users@httpd.apache.org
Cc: Arianna Manlio <ar...@yahoo.com>
Inviato: Giovedì 8 Marzo 2012 16:49
Oggetto: Re: [users@httpd] "client" or "request" meaning
> So, what is a "connection"?
A connection is a single I/O channel between hosts (TCP,UDP, UNIX SOCKETS)
> If I connect to my home webmail, I see several connection, even if I the only user.
> This means that 5 or 6 "clients" are already reserved?
>
When you connect to a website u use about 4/8 connections (images, css, ajax).
The number of connection depend on browser type, server configuration and
average load, network latency.
--
Simone Caruso
IT Consultant
+39 349 65 90 805
---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@httpd.apache.org
For additional commands, e-mail: users-help@httpd.apache.org
Re: [users@httpd] "client" or "request" meaning
Posted by Simone Caruso <in...@simonecaruso.com>.
> So, what is a "connection"?
A connection is a single I/O channel between hosts (TCP,UDP, UNIX SOCKETS)
> If I connect to my home webmail, I see several connection, even if I the only user.
> This means that 5 or 6 "clients" are already reserved?
>
When you connect to a website u use about 4/8 connections (images, css, ajax).
The number of connection depend on browser type, server configuration and
average load, network latency.
--
Simone Caruso
IT Consultant
+39 349 65 90 805
---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@httpd.apache.org
For additional commands, e-mail: users-help@httpd.apache.org
Re: [users@httpd] "client" or "request" meaning
Posted by Tom Evans <te...@googlemail.com>.
On Thu, Mar 8, 2012 at 2:35 PM, Arianna Manlio <ar...@yahoo.com> wrote:
> Hi,
> sorry for previous message.
> I'm trying to fully understand the meaning of "client" or "request" concepts
> in Apache.
> For example:
>
> http://httpd.apache.org/docs/2.2/mod/mpm_common.html#maxclients
>
> Description:Maximum number of connections that will be processed
> simultaneously
>
> ...
> The MaxClients directive sets the limit on the number of simultaneous
> requests that will be served.
>
> So, what is a "connection"?
> If I connect to my home webmail, I see several connection, even if I the
> only user.
> This means that 5 or 6 "clients" are already reserved?
>
> Thankyou very much.
>
A client is an actor that makes requests. A user agent (eg a browser)
may have several simultaneous clients making requests.
When a client establishes a connection to the server, it is taking up
one slot. When it disconnects, the slot is then free again.
If the request is made with 'Connection-Type: Keep-Alive', then the
web server may choose not close the connection once it has sent the
response, and may wait for another request to be made over that
connection. For all MPM apart from event MPM, this will also take up a
slot. This behaviour is controlled by "KeepAlive" and
"KeepAliveTimeout" directives.
For the prefork MPM, you initially have "StartServers" slots. If there
are ever less than "MinSpareServers" slots, it will add another slot.
If there are ever more than "MaxSpareServers", it will remove a slot.
It will never have more than "MaxClients" or "ServerLimit" slots.
For the worker and event MPM, you initially have "StartServers" *
"ThreadsPerChild" slots. If there are ever less than "MinSpareThreads"
slots, it will add an additional "ThreadsPerChild" slots. If there are
ever more than "MaxSpareThreads", it will remove "ThreadsPerChild"
slots. It will never have more than "MaxClients" or "ServerLimit" *
"ThreadsPerChild" slots, whichever is smaller.
If you are using winnt MPM, ask someone else!
A good way to understand this is looking at the text scoreboard
representation on the mod_status server-status page.
Cheers
Tom
---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@httpd.apache.org
For additional commands, e-mail: users-help@httpd.apache.org