(((cachedir-size-KB/avg cache obj size -KB)/256)/256)*2= L1 dir. (L2
will always 256)
you can punch that in google ;)
mike
At 12:00 PM 4/13/2007, Brian Elliott Finley wrote:
Thanks, Adrian,
I'm trying the settings changes you have recommended. They now look like:
cache_mem 200 MB
maximum_object_size_in_memory 2048 KB
1. Do you have any recommendations with regard to the number of L1
and L2 subdirectories for the cache_dir settings?
2. Should I expect any performance advantages in 2.6, or just easier
configurability for the way I'm using it? I'm satisfied with my
current accelerator related settings, and would prefer to use the
Ubuntu package from a maintenance perspective, if possible.
Cheers,
-Brian
Adrian Chadd wrote:
> On Fri, Apr 13, 2007, Brian Elliott Finley wrote:
>
>
>> I have a tentative squid configuration that includes two local
>> independent 72G disks for cache on each machine, and the following
>> relevant details. I'm pretty sure I'm way off on the object size stuff:
>>
>> cache_mem 1000 MB
>> maximum_object_size 5120000 KB
>> maximum_object_size_in_memory 1024000 KB
>> cache_dir aufs /var/spool/squid/cache1 51200 16 256
>> cache_dir aufs /var/spool/squid/cache2 51200 16 256
>> httpd_accel_host localhost
>> httpd_accel_single_host on
>> httpd_accel_uses_host_header on
>>
>
> Squid will be pretty horrible at caching those large ISOs in
memory at the moment.
> Your best bet will be to set cache_mem relatively low (couple
hundred megabytes),
> the max obj size in memory being low (megabyte or two); and rely
on OS disk caching.
>
> Use Squid-2.6; and read the release notes and FAQ for the
directive changes.
> That replaces the httpd_* lines above that were used for
squid-2.5 and earlier.
>
>
>
> Adrian
>
>
--
Brian Elliott Finley
Linux Strategist, CIS
Desk: 630.252.4742
Cell: 630.631.6621
