Open Bug 1515163 Opened 7 years ago Updated 3 years ago

Excessive telemetry pings for top stories personalizations

Categories

(Firefox :: New Tab Page, enhancement, P3)

Product:
Firefox
Component:
New Tab Page
Type:
enhancement

Tracking

()

Tracking Flags:
Tracking Status
firefox66 --- wontfix

People

(Reporter: nanj, Assigned: thecount)

Details

We've observed a huge volume of performance pings for Top Stories personalization. In particular, `PERSONALIZATION_V1_ITEM_RELEVANCE_SCORE_DURATION` and eventually `PERSONALIZATION_V2_ITEM_RELEVANCE_SCORE_DURATION` once we switch over to the v2 personalization. Looks like we send one such ping on each newtab load in the current implementation. Apparently that's unnecessary for the performance monitoring, it also adds a lot of overheads to the data pipeline. Let's figure out what's the most appropriate user base and frequency to collect this particular metric. For the time being, we will add some filters in the data pipeline to reduce the impact.
A hotfix landed in the data pipeline to exclude those pings. We will keep it until this gets fixed on the client side.
Assignee: nobody → sdowne
Iteration: --- → 66.3 - Jan 7 - 20
Priority: -- → P3
Iteration: 66.3 - Jan 7 - 20 → 67.1 - Jan 28 - Feb 10
Iteration: 67.1 - Jan 28 - Feb 10 → 67.2 - Feb 11 - 24
status-firefox66: affected → wontfix
Iteration: 67.2 - Feb 11 - 24 → ---
Component: Activity Streams: Newtab → New Tab Page

Pretty sure this ping (and similar ones) got removed in bug 1680805.

We can probably close this, and also consider removing the hotfix if it is still in there.

Severity: normal → S3
You need to log in before you can comment on or make changes to this bug.