Home > Programming, Servers & Scripts > Hosting, Servers & Security

---

The Ultimate Optimized Prosper202 & Tracking202 Server Setup (17)

---

My Fancy whiteboard video showing you a sample setup for high volume click deployment

---

Illustration sucked but the information was spot on.

---

Nice Video, anything like this for optimizing CPV Lab?

---

Bummer, I was thinking if Tracking202 didn't work out, I'd become an artist.

---

As much as I want you to use Prosper202, this setup will work with almost any software backend.

The only thing is I don't know if CPV Lab supports Memcached and also if you can install the software on multiple domains/machines without buying more licenses. If it does you are all set.

---

Do the click servers still rely on the insert_id from the "Main Database" server to populate the t202_subid and pass on the user?

If so, isn't that where the bottleneck would remain... at the mysql server inserting all the clicks?

---

You are correct about that.

The video was mainly meant to show what people can do with the current p202 code base.

Using a combination of message queues, workers, redis and code modification on the p202 side of things, the bottleneck is minimalized or eliminated.

---

Bring back wacom wars!

---

Haha Yes! I need more excuses to use my wacom tablet.

I used my new Bamboo for that vid.

---

1. All your reports are still limited to the performance of one mysql instance. And then you still run into the issue of mysql having a hard time handling a select count on 10 million rows of data.
2. I've yet to see a prosper install that actually benefited from having a load balancer, you can send millions of clicks an hour to a litespeed box provided you never run reports on that database instance. If you replicate it to another machine then run prosper there it would be your best bet.
3. Caching is done at mysql for repetitive querys with query cache, memcache is additional overhead for a predefined reply that's being answered over and over by mysql without hassle. If you run memcache locally on each webserver it allows redirects to work if your mysql server fails right? AFAIK that's how prosper202 was intended to function.


Will we ever see a new version of P202? One that shards out the database and correctly builds partitions? That would be most excellent!

---

Too bad you have to do this sort of stuff very early in the scaling process with PHP & MySQL applications :/ With proper technologies for this sort of stuff I bet only few affs here push such a volume that they would have to even think about using multiple servers.

Can you tell me your definition for "high volume click deployment"?

---

I would say hes talking about people with low end servers running stock installs of apache.

I would agree, none of our large customers are running 202 or cpvlab, all have custom rolled software on much better database technologies.

---

With current version of Proser202, yes reporting is still slow when you get into the millions of rows level. However having a read only db for reports ensures your database for writes and redirect is not slowed down when you are logged in running reports. Reporting on the hosted version is almost updated and once live in the next few days, everything will be speedy. (Almost instant)

The load balancer is for scalability and high-availability. Even if a litespeed box can handle millions of clicks an hour, when that box crashes, you are going to need a backup to immediately take over or a lot of $$ will be flushed down the drain. If you are doing millions of clicks an hour, I'm pretty sure the losses from one hour of downtime is several times that of an additional server or two behind a load balancer.

Yes memcached is useful for multiple reasons. The built-in mysql query cache works fine for some instances but for something like Prosper202, it's almost useless. The reason for this is that the cache get invalidated whenever anything in the table changes. With memcached you have more control over what to expire and when to expire it. If one result changes, only that cached result is updated. Also, like you mentioned, if the prosper202 database goes down, results stored by memcached can still be used for redirects etc.[/QUOTE]

Yes, people on the SaaS Tracking202 ClickServer platform have been enjoying constant updates for a while now. I can provide so much more value to my SaaS customers than I could ever provide to self-hosted Prosper202 users. Updates are automatically pushed out as soon as they are ready. When someone needs a quick new feature or fix I can get it to them and everyone else almost right away.

Food for thought since I hear this all the time.
Random Affiliate: I don't want to use a hosted tracking solution because "they" will have access to all my data and see what I'm doing.[1]
Hosted Tracking Solution Provider: So are you hosting your own server in your basement or something? Do you realize your web hosting company also has access to all your data? [2]
RA: No...
HTSP:


[1] If you are doing shady stuff or feel the need to hide what you are doing, please don't even signup for Tracking202. I don't want your biz or the risks tied to it. I know that just reduced my target market to two affiliates.

[2] Not a jab at Tyler and the BH team, just in case it gets misinterpreted. They have been, and are currently awesome! I know Tracking202 is not for everyone, if you want to go with P202 or any of the other self-hosted trackers you can't go wrong hosting with BH. I just wanted to point out that unless you have some sort of secure environment where only you and your trusted employees have physical access to the servers, there is some 3rd party that will be able to look at and access your data. It's all about finding the right partner, one that you can trust to have your best interests at heart.

---

Thanks for the feedback Nana.

Correct me if I'm wrong, if you have the current version of 202. 1.7.2, you can actually turn off mysql with memcache enabled and everything will continue like it never happened? I wasn't aware you had a timeout mechanism that allowed it to basically ignore the non responding database connection.

If so we will need to begin leveraging this as an upgrade from Starter to higher tier vps that include memcache standard.

---

I read the whole thread and I didn't understand if i have to turn memcache ON or not on my Hybrid/VPS + P202.
(My bad of course)

BTW I only have 700k clicks ATM

---

Turn it on

---

Yep, turn Memcached on. It'll make a big difference: http://prosper.tracking202.com/blog/...ect-technology

---

Home > Programming, Servers & Scripts > Hosting, Servers & Security