On 20/03/2015 1:07 p.m., Dan Charlesworth wrote:
> Well I got 3.5.2 into production for a few hours and Bad Things happened:
>
> *1) A hefty performance hit*
> Load average was maybe a tad higher but CPU. memory and I/O were about the
> same.
> However the system seemed to top out at around 40 requests per second (on a
> client that usually hits 100—150 rps) and squid became very slow to respond
> to
> squidclient requests:
> [root@proxy-LS5 ~]# time squidclient -p 8080 mgr:utilization | grep
> client_http.requests
> client_http.requests = 40.965955/sec
> client_http.requests = 41.168528/sec
> client_http.requests = 42.111847/sec
> client_http.requests = 166646
>
> real0m7.163s
> user0m0.002s
> sys0m0.006s
>
> *2) Lots of Segment Violations*
> These obviously suck. Backtrace attached.
Still with symbols erased so I cant see what is going on :-(
("HackXBack" is having a very similar set of issues, but on different
traffic)
>
> Just cannot win. Is it possible these two issues are due to the patch for
> #4206?
>
Doubtful, 4206 patch was only affecting the tunnel.cc code handling for
CONNECT payloads. Your assertion is in client_side.cc
FWIW, the sponsor of that patch is happily running a 3.5.2 snapshot in a
very busy production system (~975 RPS at peak) with no problems reported
to me since it went live.
We did find and fix a few of the other bugs that are patched in the
snapshot to get it to that state though. So if you are having problems
with the basic 3.5.2 bundle the latest snapshot may be worth a try as well.
There are also some patches in squid-4 that I'm due to be backporting in
the next few hrs related to worker security permissions (being denied
when they should be allowed), and PID fiel issues
Amos
_______________________________________________
squid-users mailing list
squid-users@lists.squid-cache.org
http://lists.squid-cache.org/listinfo/squid-users
