News for hackers. Stuff that matters.

A comment on Every Byte of a TLS Connection Explained and Reproduced. Parent comment

Re:Every Byte of a TLS Connection Explained and Reproduced by logicallee on Friday October 12, 2018 @08:49AM (#18201043)
Unrelated but: based on your understanding of establishing a TLS session with a server, and then traffic through that connection, do you think the new Gmail user interface for the web (desktop) is sufficiently speedy?

The reason I ask in this thread is that this thread treats some of the low-level minimum traffic necessary between clients and servers.

[ Parent | on HN ]
Re:Every Byte of a TLS Connection Explained and Reproduced by nebulous1 on Friday October 12, 2018 @09:03AM (#18201112)
Sufficiently speedy for what?

It's not clear what you're asking. Gmail obviously runs over TLS. It also seem pretty nippy to me, but TLS only has a minor impact on the speed.

[ Parent | on HN ]
Re:Every Byte of a TLS Connection Explained and Reproduced by logicallee on Friday October 12, 2018 @10:12AM (#18201528)
>It also seem pretty nippy to me

OK. (my experience since the redesign is the opposite.)

[ Parent | on HN ]
Re:Every Byte of a TLS Connection Explained and Reproduced by nimos on Friday October 12, 2018 @10:47AM (#18201777)
The TLS overhead is pretty negligible for gmail. Even though there are a lot of steps here it is only 2 round trips for the handshake. Gmail will also use TLS 1.3 (this is 1.2) if your browser supports it which cuts that down to one round trip.[0]

https://www.cloudflare.com/learning-resources/tls-1-3/

[ Parent | on HN ]
Re:Every Byte of a TLS Connection Explained and Reproduced by pjc50 on Friday October 12, 2018 @11:09AM (#18201916)
Gmail was using TLS since day 1. If it's slow for you the first likely culprit is the sheer weight of Javascript and DOM work, followed by making more web requests than necessary.
[ Parent | on HN ]
Re:Every Byte of a TLS Connection Explained and Reproduced by logicallee on Friday October 12, 2018 @01:11PM (#18202919)
>the sheer weight of Javascript and DOM work, followed by making more web requests than necessary.

can you (or anyone) put this into quantitative terms? How much are we talking about here? I realize this is a bit off-topic, but the topic is "every byte explained", so I think the people who are interested are in the right place to discuss it.

[ Parent | on HN ]
Re:Every Byte of a TLS Connection Explained and Reproduced by Obi_Juan_Kenobi on Friday October 12, 2018 @02:00PM (#18203319)
You can see a lot of what's going on with a e.g. DevTools in Chrome. Right click -> inspect

You'll want to go to the performance tab, and then record and reload the page (ctrl-shift-e). For me, about 3/4ths of the time is spent 'scripting' which is 'JS and DOM work'.

It's not terribly enlightening, though, because all the JS is minified and takes some work to understand.

[ Parent | on HN ]
Re:Every Byte of a TLS Connection Explained and Reproduced by logicallee on Friday October 12, 2018 @02:40PM (#18203669)
how much time is that for you? How does it compare to another dynamic site such as the one we're on (HN) when you're logged in?
[ Parent | on HN ]
Re:Every Byte of a TLS Connection Explained and Reproduced by taco_emoji on Friday October 12, 2018 @11:05AM (#18201895)
What does TLS have to do with the Gmail redesign? It used TLS before the redesign, didn't it?
[ Parent | on HN ]
Re:Every Byte of a TLS Connection Explained and Reproduced by logicallee on Friday October 12, 2018 @11:21AM (#18202018)
It gives a target or minimum for a fast and lightweight secure web application.
[ Parent | on HN ]