Re: [squid-users] R: [squid-users] R: [squid-users] cache size and structure

Riccardo Castellani wrote:
>> Exactly, and vice versa. If they can connect to each other. And, if they
>> are not behind slow links, although it's probably they are (otherwise there
>> would be no need for 3 caches, right?)
>
> The reason for 3 caches (1 parent + 2 child) because I have about 1700
> Windows clients along area of about 60-70 miles, which I divided into 3
> zones (A,B,C):
>
> Squid parent A is necessary for 1st zone
> Squid child B is necessary for 2nd zone
> Squid child C is necessary for 3rd zone
>
>
> My network has 2 star centers (1st zone-A, 3rd zone-C) which are linked
> together by 6 Mbps link; 2nd zone (B) is a branch of 1st zone (A) and it's
> linked to it by 11 Mbps.
> There is a unique Internet link (50Mbps) and it's located where there is 1st
> zone (A), so Squid A is the PARENT.
> Both 1st and 3rd zone has several branches (links from 128 Kbps until 1
> Mbps), being network stars, so Squid A,C serve many clients:
>
>
>
> Child B
> 2nd zone
> 11 Mbps
> 600 users
> -----
> Parent A
> 1st zone
> 50 Mbps
> 800 users
> -----
> Child C
> 3rd zone
> 6 Mbps
> 300 users
>
>
>
> Squid A serves about 800 users and squid B,C
> Squid B serves about 600 users
> Squid C serves about 300 users
>
>
> This is reason for having 3 caches, what do you think my child caches
> configured as neighbours to each other ?
>

Given that topology. I'd say no sibling B and C together would not add
much if anything over using A as a parent with Internet access.

Amos

>
>
> -----Messaggio originale-----
> Da: Matus UHLAR - fantomas [mailto:uhlar_at_fantomas.sk]
> Inviato: Thursday, July 02, 2009 5:36 PM
> A: squid-users_at_squid-cache.org
> Oggetto: Re: [squid-users] R: [squid-users] cache size and structure
>
>>> No, it is not. It may be 1mbps .OR. 76GB for week. it can't be anything
>>> "per second for week". You may mean 1mbps during weekdays, 1mbps during
>>> the whole week, 1mbps average.
>
> On 30.06.09 19:06, Riccardo Castellani wrote:
>> I want to say if weekly average of http traffic is 1 Mbps (monitored by
>> mrtg tools), all http traffic, which goes to my squid, is 76 GB in a
>> week.
>
> Aha. So, you should have 76-152 GiB of disk cache on a few fast disks, if
> you can afford that... along with a few gigs fo ram.
>
> don't put too much of cache on one disk, it can slow you down. You can start
> with e.g. 15GiB and increase by time, until you'll notice increase fo
> response times. In such case, keep the L1 on 128.
>
>> infact mrtg gives me these information:
>> maximum peak for day
>> traffic average for day
>> ...for week
>> ...for month
>>
>> Do you understand my calculates ?
>>
>>> ok, are your child caches configured as neighbours to each other?
>> both squid (B,C) have configured as parent cache squid A
>> I don't know what means "configured as neighbours to each other". Do you
>> reference B as neighbours to C ?!
>
> Exactly, and vice versa. If they can connect to each other. And, if they are
> not behind slow links, although it's probably they are (otherwise there
> would be no need for 3 caches, right?)
>
>

-- 
Please be using
   Current Stable Squid 2.7.STABLE6 or 3.0.STABLE16
   Current Beta Squid 3.1.0.9