3 ms·
A quick test I did just now. Response from google via Tor: 208 ms. Response from google without: 32 ms. To be fair I am basically on a trunk line via my univ
by SolarNet 10y ago
A quick test I did just now.
Response from google via Tor: 208 ms.
Response from google without: 32 ms.
To be fair I am basically on a trunk line via my university.
I mean you are right though, a domestic WiFi connection is likely to be in the 200 ms range, so another 200 ms on-top of that might not be as big of a deal, but I would suspect it would still end up being closer to 500 ms to get a response. Google made a point where anything over 200 ms feels slow to users. Tor is definitely going to push everything over that.
- vidarh 10y ago> a domestic WiFi connection is likely to be in the 200 ms range My wifi connection gives me ~18ms roundtrip to Google, and about 8ms extra to work, and ~50ms roundtrip from my moms house in Norway where I am currently, via her wifi, to my home server in the UK (and ~18ms roundtrip to Google from here too). These are nothing special for developed countries - just regular consumer connections. When I've been on business fibre subscriptions we've consistently gotten better results. EDIT: I initially wrote "maybe 5 years ago", without thinking. Some additional observations: While ~200ms roundtrips to a site was a thing going back long enough, first hop latencies even on dialup was rarely even 100ms. I know: I ran an ISP, and had to deal with irate customer if latency from them to their nearest games servers got to that kind of level, even in the mid 90's. SSH connection roundtrips start becoming painful in the ~120ms roundtrip range, and it's been a decade plus since that's been a problem other than when managing a slow system on the US west coast or Asia for me (connecting from Europe). Beijing or New Zealand has been in the 200ms+ range for me. If anything closer is in that range, it's a sign something is wrong.