Home > Other Systems (CPVLab, iMobiTrax, P202, Track Revenue, Click, Google Analytics, etc.) > Normal Prosper202

Prosper202 with multi click servers (8)

07-24-2013 02:32 PM #1 sarsap (Member)
Prosper202 with multi click servers

Hey guys,

Does anyone know how you can scale up p202 with more click servers?

Using a load balancer to redirect the traffic to the different servers is ideal to ease the load but it seems that prosper needs to be installed seperately on each backend node and I can't migrate the stats together from the seperated click servers.

I want 1 node for the platform interface, 3 clicks servers, 2 db servers.
It involves some PHP editing on p202 I guess.

Anyone got it done (other then the hosted Tracking202)?

Thanks

07-24-2013 03:15 PM #2 nusolutionz (Veteran Member)

there is a good blog post/video on the t202 page http://prosper.tracking202.com/blog/...2-server-setup

nana (nana@tracking202.com) from t202 is a member here too..maybe he can help you with that.

07-24-2013 04:21 PM #3 sarsap (Member)

Yeah, I've seen it. Just don't know where to add the line in PHP to tell prosper that it should divide the traffic between the different click servers

07-25-2013 02:52 PM #4 caurmen (Administrator)

Unfortunately it'll probably be a bit more complex than using a single line of code. I'd recommend outsourcing setup like this to an expert - load-balancing is big, hairy, complicated stuff. (I'd probably outsource it if I was going down this route for tracking.)

How many clicks are you currently seeing a day? You may not need to move to this sort of solution unless you're seeing huge volume.

07-25-2013 05:03 PM #5 sarsap (Member)

Something of 50k hits a day but campaigns are getting scaled and it's not long before I hit 500k-1m a day.
I want the flexibilty to scale the servers up when needed by adding more servers, avoiding downtime and pausing campaigns on traffic sources that way when migrating.
Also I was thinking of MySQL Cluster for multiple db servers, you think it can work with Prosper or I should concetrate on something else?

07-26-2013 12:42 AM #6 Mr Baffoe (Veteran Member)

It's actually quite simple (no coding needed) if you are using 1 db server.

1. Install P202 on each of the servers
2. Make sure each of the installs use the same tracking domain
3. Have each install use the same db server
4. Put everything behind a load balancer

If you are going to be doing custom coding, then I'd recommend having a replicated db for just for reporting purposes so that the main db is only used for writing click info etc.

One of the added benefits of a setup like this is knowing that you don't have a single point of failure for your click tracking (especially if you have a stand by db server that will automatically be promoted to a master db server in case the main one goes down)

07-26-2013 04:28 AM #7 getzlaf15 (Member)

Quote Originally Posted by Mr Baffoe View Post
It's actually quite simple (no coding needed) if you are using 1 db server.

1. Install P202 on each of the servers
2. Make sure each of the installs use the same tracking domain
3. Have each install use the same db server
4. Put everything behind a load balancer

If you are going to be doing custom coding, then I'd recommend having a replicated db for just for reporting purposes so that the main db is only used for writing click info etc.

One of the added benefits of a setup like this is knowing that you don't have a single point of failure for your click tracking (especially if you have a stand by db server that will automatically be promoted to a master db server in case the main one goes down)
You have 1 single point of failure, DATABASE server.

Now you can cache redirs, but the logging of the clicks still has to hit the db.

You also should be able to handle more then 500k on a single box, if you get enuff ram and ssd's.

07-26-2013 09:34 AM #8 caurmen (Administrator)

I'd recommend having a replicated db for just for reporting purposes
Definitely - that's probably the simplest way to leverage multiple DBs in a situation like this. You could even then add additional functionality, like summary tables, to speed up reporting on the reporting db without adding additional load to the main db. If you can reduce the overhead from the COUNT(*) requests in the reporting doing this, you can probably scale pretty massively.

Home > Other Systems (CPVLab, iMobiTrax, P202, Track Revenue, Click, Google Analytics, etc.) > Normal Prosper202