On 06/11/2013 08:19 PM, Matthew Ceroni wrote: > But is there a config setting (prior to the workers option) that > controlled how many concurrent connections squid could handle? Using > the Apache example again where you configure Childs, > MaxThreadsPerChild, etc. Is there anything like that in squid? In addition to other good "no, there is not such a limit" responses on this thread, I recommend carefully reading Section "Current Status and Architecture" at http://wiki.squid-cache.org/Features/SmpScale to understand the key differences between Apache "I will schedule my requests" and Squid "OS will schedule my connections" architecture. Alex. > On Tue, Jun 11, 2013 at 6:36 PM, Marcus Kool > <marcus.kool@xxxxxxxxxxxxxxx> wrote: >> >> >> On 06/11/2013 06:43 PM, Matthew Ceroni wrote: >>> >>> We are running squid as our primary proxy here at my office. >>> >>> What I am noticing is that connectivity is fine but every now and then >>> the browser sits with "Sending request". If I hope on the proxy and >>> view the access log I don't see it logging my request. After a few >>> seconds, sometimes as many as 10 - 15, the request comes through. >>> >>> My thought process is that the request is getting queued. I did a >>> little research about maximum concurrent connections but all I came >>> across was how to limit a specific user to max concurrent connections. >> >> >> There is too little information to make a conclusion but >> one should note that the HTTP command is only logged _after_ it has >> finished. >> So if you upload something large or if the webserver needs 15 seconds >> to process the request before it replies with a "thank you" >> it is normal to see the HTTP command only after 10-15 seconds in the log >> file. >> >> In case you still have doubts, you need to raise debug levels >> to find out what Squid is doing with the HTTP request. >> >> Marcus
