Re: [squid-users] peer selection with weight=N

> fre 2010-02-19 klockan 03:08 -0200 skrev H:
>
>> Thing is, all three as parent with no-query round-robin get equal load as
>> supposed, but, giving one (any) of them weight=2 makes no difference, still
>> gets the same load.
>
> How much traffic do you have?

 10Mbit/s plus 8Mbit/s on each parent cache

>
>> So I thought doing this
>>
>> cache_peer parent_IP parent tport uport no-query [weight=2]
>> cache_peer parent_IP parent tport uport no-query round-robin
>> cache_peer parent_IP parent tport uport no-query round-robin
>
> The peers all need to be configured equal except for the weight.
>
> For non-ICP/HTCP peers only round-robin has a definition of weight. The
> other peering types all select just one or a ordered list..

well, it was a try since weight does not weight ... btw, the above problem
(not weighting) applies to icp as well

>
> Correct. Siblings are only sharing cache, not uplink. What differs a
> sibling from a parent.
>

ok, but then this

# use 'allow-miss' to disable Squid's use of only-if-cached when forwarding
requests to siblings.

eventually needs better explanation/clarification

and the returned erro needs revision because it comes up ERR_ACCESS_DENIED and
should be better ERR_ONLY_IF_CACHED_MISS

H
(17)8111.3300
Received on Sat Feb 20 2010 - 05:42:38 MST