Connect & Share

Cluster Setup for an Autosurf Website

Over the years, mutual traffic exchange programs have been gaining popularity as a medium to promote websites. Most of these programs/websites use autosurf technogies to generate hits for their advitiser or member's websites. Various HYIP and Paid traffic exchange programs using autosurf scripts as their base exist on the internet. The cluster setup we did was for a site which was purely designed for mutual traffic exchange with no paid services. The member sites needed to add banners and ads from the parent website in lue of the traffic exchanged via the site. [singlepic=11,320,240,,] This site gained a huge membership base in just a few months and had traffic which could not be manged by a single dedicated server. The site involved an autosurf bar which checked for the banner/ads existence on the member site and rotated it amongst the members every few minutes. The amount of hits the member's website would receive is dependent on the amount of sites he would surf via his own autosurf area.The cluster we setup had the structure as below: [singlepic=10,320,240,,center] WebServers: The webservers were the most busy nodes of this cluster. Their site was all about generating http traffic and their members were on the site almost all the time. The autosurf structure made sure that no member was idle and so the http hits were continous and enormous in number. We had to use 3 webservers to be able to manage the amount of traffic this site was getting. Each of the webserver nodes was setup with Lighttpd + PHP as Fastcgi for faster site performance and dynamic page generation. The configuration for the webservers we used was:
  • Intel Pentium Dual Xeon 2.8 Processor
  • 2GB DDR2 RAM / 160GB SATA HDD Drive
  • CentOS 4.6
  • 1000Mbps Uplink
  • Private LAN Connections to other Nodes on the Cluster
Master Mysql Server: All the three webservers connected internally via private switch to the master Mysql server. All the site's membership data and hits stats were being stored in the database and database traffic was huge as well as each hit was being logged into mysql. The client needed managed mysql backups and redundancy and so mysql replication was used for the cluster. Due to the amount of mysql activity on the master mysql server, generation of backups from this node was almost impossible. We used replication to sync the db data on the slave server and used the slave server for generating mysql backups. The configuration we used for the Mysql Server is as below:
  • Intel Pentium Quad Core Q6600 Processor
  • 8GB DDR2 RAM/ 1x300GB SCSI 10k RPM Drive
  • CentOS 4.6
  • 100Mbps Uplink
  • Private LAN Connections to other Nodes on the Cluster
The slave Mysql server also acts as the mail server for the setup. The mailing activity for the site is moderate and so only one mail server is being used.
  • Intel Pentium Quad Core Q6600 Processor
  • 4GB DDR2 RAM/ 1x300GB SCSI 10k RPM Drive
  • CentOS 4.6
  • 100Mbps Uplink
  • Private LAN Connections to other Nodes on the Cluster
This setup distributes the traffic for the site to the three nodes using round robin DNS which is managed by the TTL. Comments are welcome as always.

Leave a Reply