PLACES_AUTOCOMPLETE_6_FIRST_RESULTS_TIME_MS histogram regressed the 25/11

RESOLVED FIXED

Status

()

Toolkit
Places
P3
normal
Rank:
31
RESOLVED FIXED
3 years ago
2 years ago

People

(Reporter: rvitillo, Unassigned)

Tracking

unspecified
x86
All
Points:
---
Dependency tree / graph
Bug Flags:
firefox-backlog +

Firefox Tracking Flags

(Not tracked)

Details

(Whiteboard: [unifiedautocomplete][watch][fxsearch])

Please see http://alerts.telemetry.mozilla.org/index.html#/detectors/1/metrics/957/alerts/?from=2014-11-25&to=2014-11-25
(Reporter)

Updated

3 years ago
OS: Mac OS X → All
I thought this was when we disabled unifiedcomplete but that happened on 26 (see bug 1105456)... So this could have 2 reasons:
1. could be the fact now for the FIRST search in a session we must fetch keywords, though that patch has been backed out for now
2. could be pre-selecting the first entry somehow caused more reflows

Unfortunately it's very hard to say now, cause we had to disable unified on 26 and now the histogram is measuring OLD autocomplete code...
Blocks: 995091
(Reporter)

Comment 2

3 years ago
Also PLACES_AUTOCOMPLETE_1ST_RESULT_TIME_MS regressed: http://alerts.telemetry.mozilla.org/index.html#/detectors/1/metrics/700/alerts/?from=2014-11-27&to=2014-11-27
Whiteboard: [fxsearch][unifiedautocomplete]

Comment 3

2 years ago
check again after enable unifiedautocomplete in nightly
Rank: 31
Flags: firefox-backlog+
Priority: -- → P3
Whiteboard: [fxsearch][unifiedautocomplete] → [unifiedautocomplete][watch][fxsearch]
Depends on: 1168811
According to the telemetry dashboard both PLACES_AUTOCOMPLETE_1ST_RESULT_TIME_MS and PLACES_AUTOCOMPLETE_6_FIRST_RESULTS_TIME_MS improved with current version of unified complete (builds >= 30th of May)
TBH, we should now measure the second entry, but still the scope of the probe was responsiveness, and we increased the perceived responsiveness.
Status: NEW → RESOLVED
Last Resolved: 2 years ago
Resolution: --- → FIXED
You need to log in before you can comment on or make changes to this bug.