-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 On 12/12/2014 4:41 a.m., Siva Prakash wrote: > Thanks for your valuable input, Eliezer and Amos. > > I have added the rough hardware and squid configuration, please > guide me out with how much request squid can handle per second, > > CPU Speed - each 3.30GHz( totally 5 processors) > > RAM - 4 GB > > NIC - one 10 GB Ethernet Adapter > > Squid Version - 3.4 > > Squid configuration - For authentication, it is integrated with AD > and lots of ACLs(1000) to block sites. > On a 3.3GHz CPU core I would expect an upper limit of around 3000 RPS. The bottlneck will be the AD processing delays. Most of HTTP performance features and mechanisms have to be disabled in order to get NTLM or Kerberos authentication to work. That reduces Squid performance by roughly a factor of 3-4. You would be lucky to get 1000 RPS per core out of the auth systems, though not all requests need the full auth latency so call it 1500 RPS max. With 4 CPU for Squid and one for OS, thats 6-12K RPS for the machine. If we assume your traffic has average object size ~40KB that measures up at around 250 Mbps combined for 4 Squid worker processes. These are very, very rough guesstimate *upper* limit numbers. The only way to be at all sure is to actually run the traffic through the proxy and find out. Squid has a lot of tuning knobs that can affect the performance. Amos -----BEGIN PGP SIGNATURE----- Version: GnuPG v2.0.22 (MingW32) iQEcBAEBAgAGBQJUir/jAAoJELJo5wb/XPRjzacIAOK9Dft9QpDtact+iKNWAVv1 KqfmZz1wHNyRc8+1do9WnKuyUvoS5WosDSE4NjCk3woc2sLVky5b0ifPsp0Z+qVx MjDGx8ka74Yl5KUAimxFhn/ZdkNLDx1CHhFkH8am8mARwFR7yA++t16biB3QvDWT zMB02DAqmJX0xRvyuqJNFUfqjaufQO3ftzFeJXTI1krCtYJxBU/Y5tQMhH/7cHhe bOfTOTPUvWRnSNmbtZKrQJae+R87a66qyAj7Rr4S+YbkyvW3d0ORW0AfDV+JWF92 hZtsWu+mVzf6n3uObg6ah+610O0T30b1FdKwfjA5ssvQDxNcShChM1MfW5ctP20= =q4IZ -----END PGP SIGNATURE----- _______________________________________________ squid-users mailing list squid-users@xxxxxxxxxxxxxxxxxxxxx http://lists.squid-cache.org/listinfo/squid-users
