On 05/03/11 17:40, christ...@wanxp.com wrote:
On 2/5/2011 11:26 AM, Eliezer Croitoru wrote:
On 05/03/2011 06:16, christ...@wanxp.com wrote:
Dear,
i installed and run 2 squid2.7 in same machine for balance CPU load
(quadcore proc). my question are can i do sibling between 2 squid in
same machine for sharing cache ? will it cause any problem in future
? any1 have experience bout this issue ?
Such configuration is one of the standard ways of getting SMP support
out of Squid older than 3.2.
http://wiki.squid-cache.org/MultipleInstances outlines the config
options that need special attention.
NP: the example socket balancing script usee TPROXY to manage the
socket layer things. NAPT can also be used with older Squid which do not
support TPROXYv4
Alternatively there is the CARP approach with a gateway parent and two
caching siblings doing the heavy lifting:
http://wiki.squid-cache.org/ConfigExamples/MultiCpuSystem
Regards,
Kristian
it seems like a good idea.
if you will bind every squid instance to other ip address or you cand
bind each one of them to a loopback interface with a mask of 32 bit
i think you can manage theoretically to make it work.
i never tried it and if it can work then i think i will do some use of
this.
but my question is: how do i bind an instance to a specific cpu\core?
Squid 3.1 and older rely completely on OS settings to bind a PID to a
core. This is not a requirement for SMP support though, just a fancy bit
of sugar.
Amos
--
Please be using
Current Stable Squid 2.7.STABLE9 or 3.1.11
Beta testers wanted for 3.2.0.5
