Back in January, the size of MobileWebClickTracking had gotten to be over 200 gb, making it so slow as to be unusable.  As a result, we split up the into 3 separate tables.

 However, it seems that >90% of the clicks are coming from the article table (or adding search created bloat) and MobileWebUIClickTracking_10742159 is now approaching 300gb.  Mostly this is due to search. I would encourage further sampling, but that would mean that beta data would be lost.  Perhaps we can split it into separate beta/stable tables and then sample stable? Any other ideas?

Phab ticket here: 

-J