Tech News

satanboy

Well-Known Member
Joined
Mar 4, 2020
Messages
11,756
Location
Batcave
 

satanboy

Well-Known Member
Joined
Mar 4, 2020
Messages
11,756
Location
Batcave
1620302196279.png
 

biometrics

Well-Known Member
Joined
Oct 17, 2019
Messages
15,386
View attachment 25342
Trying to compete with Carbonite? Seems they have little stock so far.
 

Johnatan56

Well-Known Member
Joined
Jun 22, 2020
Messages
1,116
Location
Vienna
You should read this for context, the CNET article does a terrible job of explaining it and over-promises.

Basically quite a bit faster in establishing a connection, and then the last line in that CNET article is the most important part of it, gracefully handling swapping between connections (e.g. WiFi to phone network). This is done by using a unique session identifier, and is quite a logical step forward.

So connection establishment half the time:
0*Kxoo6ErajiuLBHFE

3 trips vs 1, note though that most of the stuff you access is in a local cache, and most websites it won't matter. Things like games are UDP so will not care about a reply, so doesn't matter (which is what QUIC is based on). If e.g. in Cape Town, most of the time you hit Teraco, so 1ms vs 3ms, you won't notice the difference.

Note the don't need to repeat connection is also done in TLS 1.3, it will remember the key for the server, so most of the time that cost doesn't exist.

Forward error correction doesn't matter, it's only if 1 packet lost, most of the time you'll lose more than one if you lose a packet.

Why did I bring up the latency bit so much? Cause that's what the performance numbers are based on:
1622365792493.png
From:
Note how the performance difference for most is negligible, it's based on having more spotty connections, and that it needs to be something that usually has higher latency and a more inconsistent connection. So you need to have a good quality connection with little packet loss while having high latency. So need to put those % numbers into context:
1622365834499.png
Note that's TCP+TLS for the yellow line, so includes encryption, but think this is pre 1.3, so no caching.

1622366018479.png
Just sharing the next slide from it

So South Africa would most likely fall into South Korea similarity for a majority, but if in Cape Town or Johannesburg or within 15-20ms of it, don't think you'll really see a difference, if you are as far away as possible while still in South Africa, you can check the USA stats.

International stuff will behave better, but then again, most of the time your content is cached. It will be most interesting for things like live streaming, e.g. Twitch, since DASH (dynamic adaptive streaming over http) could potentially move to QUIC based on the browser.

------------------------------------------------------------------------------------------------------------------------------------------------------------

If you're not following the jargon, QUIC is part of the HTTP/3 spec:
- Firefox version 88 (April 2021)
- Edge 87 (old one, November 2020)
- Edge 90 (Chromium)
- Android Browser (it will have updated via Google Play store for anything newer than Android 5/6, April 2021)
- Samsung Internet 14 (April 2021).

Notable omissions:
- Safari
- Safari iOS (so any iOS device)
- IE 11
- Firefox for Android (is already built in and can be enabled via flag, expect it to be updated to be in on state within the next month or so after desktop tests are done)

If you want to check a site: https://gf.dev/http3-test
 

satanboy

Well-Known Member
Joined
Mar 4, 2020
Messages
11,756
Location
Batcave

satanboy

Well-Known Member
Joined
Mar 4, 2020
Messages
11,756
Location
Batcave
 
Top