On Sat, Dec 6, 2014 at 5:58 PM, Brighten Godfrey <[email protected]> wrote:
> > You could use an aggressive timer. But if the timer is set to less than > the typical DNS resolution time, you might as well have just sent multiple > queries to begin with. a couple thoughts there.. 1 - timeout driven multiples might have similar bandwidth costs, but if they used a consistent resolver then the privacy problem is avoided 2 - if the issue is that the OS retry is too slow for drop handling (typically measured in 1000s of ms), bringing that timer down to the 90th percentile of successful lookups (in the 100s) could have significant impact at marginal cost. Again, this is only plausible if the source of the gains you saw was due to having redundancy in the face of loss. So that's worth figuring out. Both the issue of which DNS servers are acceptable to use, and the issue of > measuring performance improvement in more realistic use cases, are > important. Does Firefox have mechanisms for testing experimental > technology like this in realistic environments? > > addons are good approaches here. We can promote them on places like mozilla hacks, and the mozilla telemetry system can be used for reporting certain kinds of anonymous results. Its well suited for reporting timings under different conditions. Thanks for your work. _______________________________________________ dev-tech-network mailing list [email protected] https://lists.mozilla.org/listinfo/dev-tech-network
