zlacker

>>akyuu+(OP)
I've used Firefox as my primary browser since the "Quantum" in 2017. Chrome still feels snappier, but Firefox's Container Tabs is hard for me to imagine losing.

>>xd1936+54
Chrome's most of the snappiness is coming from how it handles the DNS queries internally from my experience.

Pair Firefox with a fast DNS, and it's noticably faster than Chrome, for the last 3 years or so.

I discovered it accidentally, after switching to local DNS at the office. We run one of the nation-wide ones in a pretty close proximity in network terms.

>>bayind+i8
which is a fast DNS? 1.1.1.1 ? I thought the OS caches DNS anyway, so shouldn't matter much in day to day browsing.

>>EVa5I7+T8
Anything you can "time nslookup" in or under 0.03 seconds (in "real" terms).

From my desk:

    local one - 0.029 seconds
    1.1.1.1 - 0.035 seconds
    8.8.8.8 - 0.120 seconds

Normally it should be, but Firefox's behavior is very sensitive to DNS response speed. Sounds not intuitive, but I think they're not using glibc's caching, or doing something by themselves.

>>bayind+c9
Curious, where does this number comes from? (0.03 seconds)

>>jraph+Io
Nothing special. Just that if I have a DNS resolving around that timeframe, Firefox becomes noticeably faster.

All of the networks I have have a DNS server around that speed now, and Firefox works visibly faster on all of them. Possibly an intersection between human perception and hardware capabilities of my systems at hand.