[squid-users] cache_peer weighting

Hi Guys,

Wanted to double check I hadn't screwed up my config lines before
dropping a bug report....

I've got some of my parent's configured with weight's, as we're trying
out some performance optimizing code on perlbal... thing is, setting a
weight in squid doesn't seem to make a difference to the number of
requests that squid sends back to the parent. This is Squid-2.6STABLE17.

[root@cache1 ~]# grep perlbal1-80 /squidperlbal | wc -l
2
[root@cache1 ~]# grep perlbal2-80 /squidperlbal | wc -l
248
[root@cache1 ~]# grep -v perlbal[12]-80 /squidperlbal | wc -l
750

--I expected at least the inverse of the above, as unless my
understanding of squid weighting is completely incorrect, a weight of
100 should mean that peer is being used for 100 times more connections
than the weight=1 (default weight) peers, no?

Squid is configured with the following:

###ws.audioscrobbler.com & mainsite
cache_peer 10.0.0.14 parent 80 0 no-query originserver no-digest
no-netdb-exchange name=saruman2-80 round-robin
cache_peer_access saruman2-80 allow mainsite

cache_peer 10.0.0.14 parent 80 0 no-query originserver no-digest
no-netdb-exchange name=saruman2-81 round-robin
cache_peer_access saruman2-81 allow mainsite

cache_peer 10.0.0.35 parent 80 0 no-query originserver no-digest
no-netdb-exchange name=perlbal1-80 round-robin weight=100
cache_peer_access perlbal1-80 allow mainsite

cache_peer 10.0.0.35 parent 81 0 no-query originserver no-digest
no-netdb-exchange name=perlbal1-81 round-robin
cache_peer_access perlbal1-81 allow mainsite

cache_peer 10.0.0.114 parent 80 0 no-query originserver no-digest
no-netdb-exchange name=perlbal2-80 round-robin weight=100
cache_peer_access perlbal2-80 allow mainsite

cache_peer 10.0.0.114 parent 81 0 no-query originserver no-digest
no-netdb-exchange name=perlbal2-81 round-robin
cache_peer_access perlbal2-81 allow mainsite

cache_peer 10.0.0.114 parent 82 0 no-query originserver no-digest
no-netdb-exchange name=perlbal2-82 round-robin
cache_peer_access perlbal2-82 allow mainsite

cache_peer 10.0.0.114 parent 83 0 no-query originserver no-digest
no-netdb-exchange name=perlbal2-83 round-robin
cache_peer_access perlbal2-83 allow mainsite
###ws.audioscrobbler.com & mainsite Ends

I also tried removing round-robin, in case that was screwing up the
config, however, i found that this merely means all requests go to
saruman2-80.

Thanks!

-- 
Tony Dodd, Systems Administrator
Last.fm | http://www.last.fm
Karen House 1-11 Baches Street
London N1 6DL
check out my music taste at:
http://www.last.fm/user/hawkeviper