On Sun, 2005-02-13 at 11:30 -0200, H Matik wrote: Many thanks for your answer! > > You can use one cache server for your clients but this one can have one, two > or more parents. Means the backend server which is the visible cache for your > clients queries the frontend caches. So you could set up one with the > minimum_object_size 2048 KB > maximum_object_size 512000 KB > what means this one will not store on disks any objects less then 2MB and not > larger the 512MB the other you configure > maximum_object_size 2048 KB So, I could setup the backend for small object (max 2MB) while the backend for big files (from 2MB to 512MB of even bigger)?!?! > > > Then with the proper cache_peer settings the backend server should get icp > replies about what each has on disk and so you can have e fast rotating > content on the small object cache and slow rotating large objects on the > other. So you may set something like this > cache_peer large_object_ip 8080 3130 parent proxy-only (for not storing the > files again) Please pardon me, but can I setup, in a cache peering relationship via ICP, that the squid making the ICP queries do not cache the files it recieves back? > cache_peer small_object_ip 8080 3130 parent > > Depending on your client-number and/or network size you may use a backend > server without caching anything setting both peers to proxy only and a null > cache_dir if the three are talking fast enought between them I could setup the three squid on the same machine for example (thus achieving the fastest communication among them...) > > You may consider tweaking the quick_abort values on the large_object cache > also and sure you need to set refresh_patterns to your convinience. > You should set always_direct and never_direct in order to make this > combination work good. Once again, thanks for your patience! Marco
