Closed Bug 1470093 Opened 2 years ago Closed 2 years ago

The DNS_TRR_LOOKUP_TIME telemetry can't realistically be zero much

Categories

(Core :: Networking: DNS, enhancement, P1)

enhancement

Tracking

()

RESOLVED FIXED
mozilla62
Tracking Status
firefox62 --- fixed

People

(Reporter: bagder, Assigned: bagder)

Details

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

Attachments

(1 file)

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 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+
Pushed by daniel@haxx.se:
https://hg.mozilla.org/integration/autoland/rev/f9c5cbd49b98
fix telemetry::DNS_TRR_LOOKUP_TIME r=mcmanus
https://hg.mozilla.org/mozilla-central/rev/f9c5cbd49b98
Status: NEW → RESOLVED
Closed: 2 years ago
Resolution: --- → FIXED
Target Milestone: --- → mozilla62
You need to log in before you can comment on or make changes to this bug.