Squid is telling me that it can use 8192 file descriptors.

ns:~ # ulimit -Sa
core file size          (blocks, -c) 1
data seg size           (kbytes, -d) unlimited
scheduling priority             (-e) 0
file size               (blocks, -f) unlimited
pending signals                 (-i) 62844
max locked memory       (kbytes, -l) 64
max memory size         (kbytes, -m) 6847088
open files                      (-n) 1024
pipe size            (512 bytes, -p) 8
POSIX message queues     (bytes, -q) 819200
real-time priority              (-r) 0
stack size              (kbytes, -s) 8192
cpu time               (seconds, -t) unlimited
max user processes              (-u) 62844
virtual memory          (kbytes, -v) 14830240
file locks                      (-x) unlimited

ns:~ # ulimit -Ha
core file size          (blocks, -c) unlimited
data seg size           (kbytes, -d) unlimited
scheduling priority             (-e) 0
file size               (blocks, -f) unlimited
pending signals                 (-i) 62844
max locked memory       (kbytes, -l) 256
max memory size         (kbytes, -m) unlimited
open files                      (-n) 8192
pipe size            (512 bytes, -p) 8
POSIX message queues     (bytes, -q) 819200
real-time priority              (-r) 0
stack size              (kbytes, -s) unlimited
cpu time               (seconds, -t) unlimited
max user processes              (-u) 62844
virtual memory          (kbytes, -v) unlimited
file locks                      (-x) unlimited

-----Message d'origine-----
De : Eliezer Croitoru [mailto:elie...@ngtech.co.il] 
Envoyé : 27 novembre 2012 14:35
À : squid-users@squid-cache.org
Objet : Re: [squid-users] Problem publishing on Facebook via Squid 3.1.2

If the CPU ram and wait are low the only thing I can think is Low 
file-descriptors which you can see using:
ulimit -Sa
ulimit -Ha

Eliezer

On 11/27/2012 9:31 PM, Delisle, Marc wrote:
> Hello Eliezer,
> Thanks for your excellent analysis. First, there is no cache_dir involved. 
> Second, I deactivated access_log and cache_log and the problem persists.
>
> CPU does not seem to be the problem, it's mostly 80% idle with less than 0.5 
> % wait. Routing is RIP-only, but this box is IP-forwarding all traffic for 
> the whole campus.
>
> By the way, in Squid my cache_mem is set to 5000 MB.
>
> Could you elaborate on the NAT issue? Most of our users are indeed in private 
> networks and the Squid box is performing also NAT for them.
>
> My next step is to compile Squid 3.2.3 and give it a try, even though I would 
> have preferred to stay with the packages offered in this distro.

--
Eliezer Croitoru
https://www1.ngtech.co.il
sip:ngt...@sip2sip.info
IT consulting for Nonprofit organizations eliezer <at> ngtech.co.il

Reply via email to