%cpu in system - squid performance in FreeBSD 5.3

[Jeff Behl]

back from vacation...

i did try STABLE, with the same results:

FreeBSD www2.cdn 5.3-STABLE FreeBSD 5.3-STABLE #2: Sun Dec  5 21:06:14 
PST 2004     root at www2.cdn:/usr/obj/usr/src/sys/SMP  amd64


interestingly enough, i got a reply on a squid list from someone on a 
linux box who had similar results:
-
I've got a dual proc Xeon (3GHz) Linux 2.4.26 system running one squid 
2.5.5 as reverse proxy without cache, I use squidguard to route 
different path of the same domain to different clusters.

Top shows:
Cpu1 :  39.3% user,  58.0% system,   0.0% nice,   2.7% idle
-

so perhaps this is some gross problem with squid?


jeff

Sean Chittenden wrote:

>> As a follow up to the below (original message at the very bottom), I
>> installed a load balancer in front of the machines which terminates the
>> tcp connections from clients and opens up a few, persistent connections
>> to each server over which requests are pipelined.  In this scenario
>> everything is copasetic:
>
>
> Interesting... I wonder what the lock contention path is between the 
> VM and network stack.  Has anyone else noticed this in their testing?  
> Did you try a post-5.3 release or not?  rwatson@ just MFC'ed a bunch 
> of network locking fixes to RELENG_5, but none-stand out in my mind as 
> being something that'd potentially fix your issue.  Actually, he 
> probably knows better than anyone what this could be.  Some of the 
> post RELENG_5_3 commits by alc@ could explain this, however, and is 
> why I ask what the specific version/build time is for your release.  -sc
>