Affiliates:tuneup: Difference between revisions
Jump to navigation
Jump to search
| Line 26: | Line 26: | ||
** Creates heavy load on DB replicators | ** Creates heavy load on DB replicators | ||
*** Split processing DB into a DB not being constantly replicated | *** Split processing DB into a DB not being constantly replicated | ||
** Points tally uses DB too much | ** Points tally uses DB too much | ||
*** Refactor points tally process | *** Refactor points tally process | ||
*** '''consider dropping / changing points''' | *** '''consider dropping / changing points''' | ||
** Parsing mozilla.com and download.m.o log, is inefficient | ** Parsing mozilla.com and download.m.o log, is inefficient | ||
** Legacy button HTML | ** Legacy button HTML | ||
*** contact affiliates, ask them to upgrade? | *** contact affiliates, ask them to upgrade? | ||
*** when do we stop tracking these? | *** when do we stop tracking these? | ||
Latest revision as of 21:47, 12 January 2010
High Level
- Make up legacy / lost traffic
- Implement new tracking system
- Omniture?
- How can production site w/ 200k hits per day, pull from Omniture?
- Dashboard
- Hits / Downloads
- per...
- user
- button
- referrer
- total per time period (day, month, etc)
- locale
- campaign
Nitty Gritty
- Referral archives DB table is getting too large
- Save backup and prune this down
- Build aggregates out of pruned data
- Build system to compile aggregates for new data
- Log processing is inefficient
- Creates heavy load on DB replicators
- Split processing DB into a DB not being constantly replicated
- Points tally uses DB too much
- Refactor points tally process
- consider dropping / changing points
- Parsing mozilla.com and download.m.o log, is inefficient
- Legacy button HTML
- contact affiliates, ask them to upgrade?
- when do we stop tracking these?
- Creates heavy load on DB replicators