> Adrian Chadd schrieb: >> What we're really missing is a bunch of "hardware x, config y, testing >> z, results a, b, c." TMF used to have some stuff up for older hardware >> but there's just nothing recent to use as a measuring stick.. >> >> >> >> Adrian >> >> >> 2008/7/16 Chris Robertson <[EMAIL PROTECTED]>: >> >>> Luis Daniel Lucio Quiroz wrote: >>> >>>> HI folks >>>> >>>> I already know that there is not a recipe for squid. But I wonder if >>>> anyone knows an official document that lists squid requirements. >>>> >>>> Regards, >>>> >>>> LD >>>> >>>> >>> That's a bit like asking "What kind of a car should I get?". You need >>> to >>> give some details of the expected workload. >>> >>> In general, get a higher clocked CPU, as much RAM and as many drives as >>> you >>> can afford, and use regex based ACLs sparingly. >>> >>> Chris > OK - then let's start collecting some numbers with more recent hardware: > > we have a Squid 3 stable 5 on a opensuse 10.3 running on following > system for about 100 users > with adequate response times: > IBM xSeries 3250 M2 > 1x Intel Core 2 Duo E4600 2.4 Ghz/800 MHz (2 MB L2 cache) > 3 GB PC2-5300 CL5 ECC DDR2 SDRAM DIMM > 2x 250 GB SATA hard drive as a mirror configuration > > This system is doing virus-scanning with ICAP-enabled Squid through KAV > 5.5 > Kaspersky AntiVirus for Internet Gateways > AND it is doing web-content filtering with SquidGuard 1.3 > AND it is doing NTLM AUTH against the internal W2k3-ADS-domain
Thank you. Are you able to indicate the average req/sec your machine is reaching? Amos
