Thanks Amos and Hasanen for the info , much appreciated. Using 8 SAS disks should give me enough disk i/o right? I'm thinking of using razorfs with one disk per cash repository. -----Original Message----- From: Amos Jeffries [mailto:squid3@xxxxxxxxxxxxx] Sent: Friday, June 14, 2013 1:38 PM To: squid-users@xxxxxxxxxxxxxxx Subject: Re: Squid Hardware requirements. On 14/06/2013 10:15 p.m., Stephan Viljoen wrote: > Hi There, > > I need to build a proxy server for an ISP handling about 4000 ip > addresses over a 125Mbps of Internet bandwidth and were wondering what > the specs for such a server would be? It's going to be a transparent > squid server configured with Tproxy running as a bridge. > I'm thinking of using around 16GB of RAM More RAM the better. Squid will run with only a few dozen MB, but the more you can throw at it the more memory cache it can be assigned and that is the fastest response traffic. Also you *will* be aportioning the RAM between multiple Squid on this box. > , two Quad core Xeon CPU's and > about 8 SAS disks. Will this be enough or should I aim higher? Squid uses one CPU per process and uses that CPU right to the bare metal speed limits sometimes. So fast GHz ratings CPUs are better than more slower cores. > Some advice would be greatly appreciated. With a box like that go straight to 3.3 series and experiment with SMP workers to utilize more than one CPU core. Each Squid instance / worker should be able to service a least 50 Mbps per core. That does depend a lot on the request/sec rate of HTTP messages that 50Mbps is built from. The Squid processing limit is only reliably measure in requests per second. In HTTP/1.0 traffic that has typically topped out at ~500req/sec around 100Mbps, but HTTP/1.1 is a fair bit more optimized and revalidation traffic can top out at a higher req/sec on just a few Mbps. Still an 8-core box has room to scale Squid out by bumping up the worker count. Amos
