Closed Bug 847193 Opened 12 years ago Closed 12 years ago

some getpersonas calculations

Categories

(Cloud Services :: Operations: Marketplace, task)

task
Not set
normal

Tracking

(Not tracked)

RESOLVED FIXED

People

(Reporter: clouserw, Assigned: jason)

Details

Personas have an update check ping built into them. I'm not sure if we measure traffic to it at all but judging from the number of accounts on getpersonas it could be a non-trivial number. The URL for update pings is gp.com/:lang/update_check/:id. An example: > https://www.getpersonas.com/en-US/update_check/33 1) Would you grep the last week of zeus logs for getpersonas.com and total up hits per day on update_check? 2) Would adding that many hits per day to VAMO concern you? My current plan is to just 301 to VAMO and have VAMO handle sending updates to clients. Assume the same caching on the front end as add-on updates.
Assignee: server-ops-amo → jthomas
1. See below per day hits on update_check: 02-25 11252917 02-26 11206722 02-27 11098986 02-28 10913052 03-01 10121355 03-02 8971229 03-03 10002006 2. No, VAMO cluster should be able to handle this traffic without a problem.
Status: NEW → RESOLVED
Closed: 12 years ago
Resolution: --- → FIXED
thanks
Component: Server Operations: AMO Operations → Operations: Marketplace
Product: mozilla.org → Mozilla Services
You need to log in before you can comment on or make changes to this bug.