Open Bug 1753979 Opened 3 years ago Updated 1 year ago

Consider increasing the number of DNS resolver threads.

Categories

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

Product:
Core
Component:
Networking: DNS
Type:
enhancement

Tracking

()

People

(Reporter: valentin, Unassigned)

References

(Blocks 2 open bugs)

Details

(Whiteboard: [necko-triaged])

The number of parallel DNS resolutions is currently limited to 8 It has been so pretty much for since 2008.

As Brian noticed, Chrome has recently increased these limits.

This bug requires an investigation into doing the same.

Whiteboard: [necko-triaged]
Performance Impact: --- → ?

Not sure setting a perf impact is appropriate, as we can't really tell right now what the impact would be.

But umm, can't we just double the number on nightly and look at telemetry? It feels like this shouldn't be super-hard. Maybe something Marc could do? What do you think Dragana?

Performance Impact: ? → ---
Flags: needinfo?(dd.mozilla)

Yes, we are planning to perform such an experiment.

Flags: needinfo?(dd.mozilla)
Depends on: 1812009
Blocks: necko-perf

For native dns queries, I believe the probe dns_native_queuing collects the delay.
0 ms, but 32 ms at 95th percentile.

Depends on: 1840441
You need to log in before you can comment on or make changes to this bug.