Re: [squid-users] investigate squid eating 100% CPU

>> the cachemanager can be usefull to see the actual activity of your squid :
>>
>> squidclient localhost mgr:5min
>>
>> gives you the last 5 min stats. (see if the n° of req/s is coherent
>> with what you expect )
>
>
> Here after the output of the mgr:5min
> It show that we are around 168 req/s
> for a cpu usage around 99%
> I don't think that 160 req/s is such a big number that can explain full CPU time.

Forgot to mention that it somtimes drops to ~30% CPU for some periods.
For example right now we are :
client_http.requests = 160.370710/sec
cpu_usage = 39.305030%

Which makes me think of some kind of requests getting it to go crazy.

[complete output here]

sample_start_time = 1364317190.222942 (Tue, 26 Mar 2013 16:59:50 GMT)
sample_end_time = 1364317490.271499 (Tue, 26 Mar 2013 17:04:50 GMT)
client_http.requests = 160.370710/sec
client_http.hits = 17.510499/sec
client_http.errors = 0.016664/sec
client_http.kbytes_in = 278.614904/sec
client_http.kbytes_out = 3589.275718/sec
client_http.all_median_svc_time = 0.092188 seconds
client_http.miss_median_svc_time = 0.097357 seconds
client_http.nm_median_svc_time = 0.000911 seconds
client_http.nh_median_svc_time = 0.016481 seconds
client_http.hit_median_svc_time = 0.000911 seconds
server.all.requests = 145.123178/sec
server.all.errors = 0.000000/sec
server.all.kbytes_in = 3294.903365/sec
server.all.kbytes_out = 269.543039/sec
server.http.requests = 130.565534/sec
server.http.errors = 0.000000/sec
server.http.kbytes_in = 2860.440352/sec
server.http.kbytes_out = 179.021024/sec
server.ftp.requests = 0.000000/sec
server.ftp.errors = 0.000000/sec
server.ftp.kbytes_in = 0.000000/sec
server.ftp.kbytes_out = 0.000000/sec
server.other.requests = 14.557644/sec
server.other.errors = 0.000000/sec
server.other.kbytes_in = 434.463013/sec
server.other.kbytes_out = 90.525348/sec
icp.pkts_sent = 0.000000/sec
icp.pkts_recv = 0.000000/sec
icp.queries_sent = 0.000000/sec
icp.replies_sent = 0.000000/sec
icp.queries_recv = 0.000000/sec
icp.replies_recv = 0.000000/sec
icp.replies_queued = 0.000000/sec
icp.query_timeouts = 0.000000/sec
icp.kbytes_sent = 0.000000/sec
icp.kbytes_recv = 0.000000/sec
icp.q_kbytes_sent = 0.000000/sec
icp.r_kbytes_sent = 0.000000/sec
icp.q_kbytes_recv = 0.000000/sec
icp.r_kbytes_recv = 0.000000/sec
icp.query_median_svc_time = 0.000000 seconds
icp.reply_median_svc_time = 0.000000 seconds
dns.median_svc_time = 0.014637 seconds
unlink.requests = 0.000000/sec
page_faults = 0.000000/sec
select_loops = 2316.561716/sec
select_fds = 0.000000/sec
average_select_fd_period = 0.000000/fd
median_select_fds = 0.000000
swap.outs = 0.000000/sec
swap.ins = 0.000000/sec
swap.files_cleaned = 0.000000/sec
aborted_requests = 2.159650/sec
syscalls.disk.opens = 0.000000/sec
syscalls.disk.closes = 0.000000/sec
syscalls.disk.reads = 0.000000/sec
syscalls.disk.writes = 0.000000/sec
syscalls.disk.seeks = 0.000000/sec
syscalls.disk.unlinks = 0.000000/sec
syscalls.sock.accepts = 105.942852/sec
syscalls.sock.sockets = 66.179288/sec
syscalls.sock.connects = 62.956477/sec
syscalls.sock.binds = 66.179288/sec
syscalls.sock.closes = 124.793135/sec
syscalls.sock.reads = 1316.883520/sec
syscalls.sock.writes = 1770.096831/sec
syscalls.sock.recvfroms = 58.203913/sec
syscalls.sock.sendtos = 30.974986/sec
cpu_time = 117.934176 seconds
wall_time = 300.048557 seconds
cpu_usage = 39.305030%
Received on Tue Mar 26 2013 - 17:09:42 MDT