Squid slow Transfers
-
Yes, I am running beta. Of course, given that the OP claims to be running 1.3 then 1.4 - yet 1.2 hasn't gone final yet, I think we've got a good range of releases for (non-)information gathering ;)
We should find out in a week or so whether the problem is related to a post 1.2 Beta2 change or whether it's hardware related.
-
Can I borrow your time machine??
-
Unfortunately somebody calling himself The Master stole it, muttering something about visiting a doctor ;)
(Even if 1.2 isn't out at the end of the month I may upgrade to the latest RC anyway so I can get NUT support back)
-
hello!
I also experience slow transfers with squid-2.6.5,pf 1.2RC3 and squidguard- 1.2.0_1 ,with squid in transparent mode.
If i disable squid all web pages goes very fast.If i enable it the speed decreases at about 20-30%.It's not a big deal for me now but i would like to have it work better… :)thank you
-
hello!
I also experience slow transfers with squid-2.6.5,pf 1.2RC3 and squidguard- 1.2.0_1 ,with squid in transparent mode.
If i disable squid all web pages goes very fast.If i enable it the speed decreases at about 20-30%.It's not a big deal for me now but i would like to have it work better… :)thank you
If disabled SquidGuard - speed slowly too?
-
yes it is slow even if i disable squidguard and even if i put the web site in exeption list to not be cached by squid.
-
yes it is slow even if i disable squidguard and even if i put the web site in exeption list to not be cached by squid.
Traffic shaper used?
-
no i'm not using ts cause i have a dual wan config.
-
no traffic shaper, but I'm seeing this too…
-
I can confirm that I experience the same slowdown when using the proxy.
No bandwidth throttling set. No Traffic Shaper used at the moment, either.
I tried setting squid's "Overall Bandwidth Throttling" to the maximum my connection allows, in case "Disabled" wasn't working as it should, but this had no effect.
My maximum downstream speed is ~350kBps but I get between 175 and 200kBps when I use the proxy.
-
To Fix Squid
add this to the /boot/loader.conf
kern.ipc.nmbclusters=32768
kern.maxfiles=65536
kern.maxfilesperproc=32768
net.inet.ip.portrange.last=65535or just delete it and replace with
autoboot_delay="1"
#kern.ipc.nmbclusters="0"
hint.apic.0.disabled=1
kern.hz=100
#for squid
kern.ipc.nmbclusters="32768"
kern.maxfiles="65536"
kern.maxfilesperproc="32768"
net.inet.ip.portrange.last="65535"you might ask why squid is so slow? its because default configuration of pfsense is router not as a server
thats why kern.ipc.nmbclusters="0" <- is set to zero. if you just simply remove this squid will be just fine.but to tune the squid i add this
kern.ipc.nmbclusters: 32768
kern.maxfiles=65536
kern.maxfilesperproc=32768
net.inet.ip.portrange.last: 65535i just figure out why squid is slow. but i don't like the binary package of squid. i'll be using the squid HEAD bec of the store_rewrite feature for caching youtubes videos and other video files and mp3.
-
hello all,
i seem to experience the same problem/situation, and configured /boot/loader.conf as suggested and re-start the squid service. but after half an hour, squid and squidguard suddenly stopped functioning… tracing the cause of the problem, i found out that /var/squid/cache occupied the available disk space, therefore stopping the services. could the modification in /boot/loader.conf caused this? can you please explain what's the effect of each line of the modification to /boot/loader.conf?
thank you very much for clearing this up.
allison
-
WOW this makes a big change to squid !!!
Thank You
Now it is helpfull and not a pain anymore
Is there anywhere a squid 3.0 based package for pfsense ?
-
The change must be made to loader.conf in 1.2.2_RELEASE as well. I was suffering from the exceptionally slow transfers until I commented out the #kern.ipc.nmbclusters="0"
@Devs
What are the advantages of this argument? Why was this changed temporarily in the 1.2/FreeBSD 6.3 Release? Any insight would be greatly appreciated. Perhaps someone could also commit a change to the Squid packages so that the loader.conf gets updated upon package installation.
