Hi all,
I am running squid proxy server integrated with Content filter Dansguardian, squidguard and clamav for Http level scanning on centos 5 .Configured webmin management tool to create and manage access control using squidguard plug in. Now it is serving request for 100 machines and Below is my hardware details.
Hardware Details
SUN BLADE 6000 2.67 GHz * 1 4 Gb RAM 2*146Gb HDD
we intend to scale proxy servers with around 7000 to 10000 users in future.Just i want to confirm whether the the above hardware is sufficient enough to serve 10000 users.If not please recommend me the server configuration i have to go for and also how to calculate the same.
And also to prevent single point of failure is it possible to configure squid in any load balancing mode (with another dedicated server) if so just guide me how to do the same or provide me the link that best explains squid proxy server in load balancing mode.
Anticipating your reply
Regards,
Craz paps
Howdy,
Regarding the Load Balancing, I find ipvsadm to be a very good package.
I'm not well-versed with squid, but for 10,000 users, I should image that hardware is not sufficient (especially if they're all requesting pages at the same time?)
My immediate hunch would be to set up a virtualised squid proxy, and then copy that across to be hosted on multiple servers. Providing it's set up in a scalable fashion (maybe NFS share for config/rules) across the entire cluster - you should be able to have a very scalable solution.
Regards,
Andy Loughran
linux-crazy wrote:
Hi all,
I am running squid proxy server integrated with Content filter Dansguardian, squidguard and clamav for Http level scanning on centos 5 .Configured webmin management tool to create and manage access control using squidguard plug in. Now it is serving request for 100 machines and Below is my hardware details.
Hardware Details
SUN BLADE 6000 2.67 GHz * 1 4 Gb RAM 2*146Gb HDD
we intend to scale proxy servers with around 7000 to 10000 users in future.Just i want to confirm whether the the above hardware is sufficient enough to serve 10000 users.If not please recommend me the server configuration i have to go for and also how to calculate the same.
And also to prevent single point of failure is it possible to configure squid in any load balancing mode (with another dedicated server) if so just guide me how to do the same or provide me the link that best explains squid proxy server in load balancing mode.
Anticipating your reply
Regards,
Craz paps _______________________________________________ CentOS mailing list CentOS@centos.org http://lists.centos.org/mailman/listinfo/centos
Regarding the Load Balancing, I find ipvsadm to be a very good package. I'm not well-versed with squid, but for 10,000 users, I should image that hardware is not sufficient (especially if they're all requesting pages at the same time?) My immediate hunch would be to set up a virtualised squid proxy, and then copy that across to be hosted on multiple servers. Providing it's set up in a scalable fashion (maybe NFS share for config/rules) across the entire cluster - you should be able to have a very scalable solution.
Squid supports cache peering, cache hierarchies, and multicast ICP. I'd setup Squid peers.
On Sat, Dec 6, 2008 at 11:38 AM, Adam Tauno Williams awilliam@whitemice.org wrote:
Regarding the Load Balancing, I find ipvsadm to be a very good package. I'm not well-versed with squid, but for 10,000 users, I should image that hardware is not sufficient (especially if they're all requesting pages at the same time?) My immediate hunch would be to set up a virtualised squid proxy, and then copy that across to be hosted on multiple servers. Providing it's set up in a scalable fashion (maybe NFS share for config/rules) across the entire cluster - you should be able to have a very scalable solution.
Squid supports cache peering, cache hierarchies, and multicast ICP. I'd setup Squid peers.
Exactly... and it is possible to have a 'URL' as your proxy. It can contain hints and be dynamic over time making it "easy" to update the proxy environment. and you have a single instruction for all your 10000 users. While some stuff can be done with DHCP, the URL trick is powerful and sets a stage such that the squid admin folk do not need to touch a complex DHCP setup.