Bugzilla

This is a simple test page that stresses the browser's dns resolution:
https://acreskeymoz.github.io/dns/dns_prefetch_and_requests.html

There are three tests, each initiated by a button press:

1. Test one dns resolution every second via dns-prefetch
2. Test 100 dns requests at once via dns-prefetch
3. Test 100 dns requests at once by loading favicons from 100 domains

This profiles captures all three
https://deploy-preview-5578--perf-html.netlify.app/public/8f8b8v1hw46427qjx9bt5rhb9j22md83jfzkzcg/marker-chart/?globalTrackOrder=504213&hiddenGlobalTracks=12&markerSearch=lookup&thread=0&v=12

1. very roughly 50-80ms / resolution
2. 160-170ms / resolution
3. 80-1800ms / resolution. (Socket thread busy with connect, handshake, cert stuff, etc).

Not clear how representitive this is of real world situations.

This is a simple test page that stresses the browser's dns resolution:
https://acreskeymoz.github.io/dns/dns_prefetch_and_requests.html

There are three tests, each initiated by a button press:

1. Test one dns resolution every second via dns-prefetch
2. Test 100 dns requests at once via dns-prefetch
3. Test 100 dns requests at once by loading favicons from 100 domains

This profiles captures all three
https://deploy-preview-5578--perf-html.netlify.app/public/8f8b8v1hw46427qjx9bt5rhb9j22md83jfzkzcg/marker-chart/?globalTrackOrder=504213&hiddenGlobalTracks=12&markerSearch=lookup&thread=0&v=12

1. very roughly 50-80ms / resolution
2. ~160-260ms / resolution
3. 80-1800ms / resolution. (Socket thread busy with connect, handshake, cert stuff, etc).

Not clear how representative this is of real world situations.