The DNS_TRR_LOOKUP_TIME telemetry can't realistically be zero much

RESOLVED FIXED in Firefox 62

Status

()

enhancement
P1
normal
RESOLVED FIXED
Last year
Last year

People

(Reporter: bagder, Assigned: bagder)

Tracking

Trunk
mozilla62
Points:
---

Firefox Tracking Flags

(firefox62 fixed)

Details

(Whiteboard: [necko-triaged][trr])

Attachments

(1 attachment)

Assignee

Description

Last year
The TRR lookup time is a full HTTPS request round-trip to the resolver, which in most practical cases will be multiple up to many milliseconds. The current telemetry shows a shocking amount of zero millisecond resolves, indicating this is wrongly measured.
Comment hidden (mozreview-request)

Comment 2

Last year
mozreview-review
Comment on attachment 8986715 [details]
bug 1470093 - fix telemetry::DNS_TRR_LOOKUP_TIME

https://reviewboard.mozilla.org/r/252012/#review258482
Attachment #8986715 - Flags: review?(mcmanus) → review+

Comment 3

Last year
Pushed by daniel@haxx.se:
https://hg.mozilla.org/integration/autoland/rev/f9c5cbd49b98
fix telemetry::DNS_TRR_LOOKUP_TIME r=mcmanus

Comment 4

Last year
bugherder
https://hg.mozilla.org/mozilla-central/rev/f9c5cbd49b98
Status: NEW → RESOLVED
Closed: Last year
Resolution: --- → FIXED
Target Milestone: --- → mozilla62
You need to log in before you can comment on or make changes to this bug.