On ons, 2008-06-18 at 01:44 +, [EMAIL PROTECTED] wrote:
I'm most interested in the squid back-end setup. Should we look at something
linux based clustering? Or should we be looking at some internal squid
process?
You don't need to cluster Squif, just a bunch of more or less
independent
Henrik Nordstrom wrote:
On ons, 2008-06-18 at 01:44 +, [EMAIL PROTECTED] wrote:
I'm most interested in the squid back-end setup. Should we look at something
linux based clustering? Or should we be looking at some internal squid process?
You don't need to cluster Squif, just a
Just consider balancing the load on source IP, or NATing the Squid
servers, as there are a number of websites that don't like a single HTTP
session originating from multiple IPs.
Long ago, far away, when I owned a managed server hosting
company... We used Foundry load balancers to
What's your workload? E.g., is it going to be used as a proxy farm for
dialup users? Broadband? If so, how many? Or, is it for an
accelerator, and if so, how much content is there?
Cheers,
On 18/06/2008, at 5:07 AM, [EMAIL PROTECTED] wrote:
I've been given a directive to build a squid
More broadband connections than anything else.
Possibly as many as 50,000 users.
No accelerator, maybe not even caching. Mostly to filter downloads, record
websites, etc. maybe with something like urldb or Dansguardian.
Do you have ideas???
Thank you.
-- Original message
If you're not caching at all and using reasonably modern hardware
(e.g., dual core, ~3Ghz), you should be able to get somewhere between
2,000 and 4,000 requests a second out of a single squid process,
depending on the average response size. YMMV, of course, and that
doesn't count the
The hard part is going to be directing requests to the proxies, and
handling failure well. I haven't done ISP proxy deployments in a long
time, so I'll leave it to others to give you advice on that part. I'm
assuming you'll want it to be transparent (e.g., use WCCP)?
If transparent, WCCPv2
50,000 customers total.
We're looking at LVS using keepalived for load balancing at the front-end.
I'm most interested in the squid back-end setup. Should we look at something
linux based clustering? Or should we be looking at some internal squid process?
Could we run multiple squid processes
