Current time: 10-15-2019, 12:03 AM Hello There, Guest! (LoginRegister)

Post Reply 
 
Thread Rating:
  • 0 Vote(s) - 0 Average
  • 1
  • 2
  • 3
  • 4
  • 5
Please elaborate on "Bytes In"
03-31-2016, 01:12 AM
Post: #1
Please elaborate on "Bytes In"
The quick start guide defines Bytes In as
Quote:This is the amount of data that the browser had to download in order to load the page. It is also commonly referred to as the "Page Size".

I found a comment by Patrick Meenan which seems to be a little more definitive:
Quote: The "bytes in" (overall) measures at the socket level and is guaranteed to be the number of bytes that came in over the wire (even if there was a problem with reporting individual requests)

But some elaboration would be helpful.
I believe "bytes in" would include all the overhead of SSL encryption, at least from my experiments, but does it include TCP overhead, etc?

Thanks
Oh and thanks for the very powerful WebPageTest tool!
Find all posts by this user
Quote this message in a reply
03-31-2016, 02:36 AM
Post: #2
RE: Please elaborate on "Bytes In"
It will include SSL (only overhead is the certificate negotiation and a couple of bytes of framing) but not TCP overhead. It intercepts the socket reads in user mode so doesn't see packet-level details.
Visit this user's website Find all posts by this user
Quote this message in a reply
03-31-2016, 07:29 AM
Post: #3
RE: Please elaborate on "Bytes In"
(03-31-2016 02:36 AM)pmeenan Wrote:  It will include SSL (only overhead is the certificate negotiation and a couple of bytes of framing) but not TCP overhead. It intercepts the socket reads in user mode so doesn't see packet-level details.

Thanks Patrick

I'll pester you just one more time.
I've included links to two tests below:
The first, a Google png file using https, the second is just the same file with straight http.
Comparing the "Bytes In" for both there is an 8K difference. Can I conclude the bytes transferred for the encrypted version of png file is 8K larger than the un-encrypted version?

http://www.webpagetest.org/result/160330...1/details/ HTTPS
Notice "Bytes In" at 30K, but in the Request Details 21.6K.
http://www.webpagetest.org/result/160330...1/details/
Notice "Bytes In" at 22K, but in the Request Details the size remains 21.6K, which seems completely reasonable to me.

21.6K is the actual size reported by other browser "network" tools for the png file from Google.
Find all posts by this user
Quote this message in a reply
03-31-2016, 07:38 AM
Post: #4
RE: Please elaborate on "Bytes In"
Sorry, yes - there is the potential for wasted bytes with TLS padding depending on how well optimized the server is and if it supports dynamic record sizes: https://www.igvita.com/2013/10/24/optimi...g-latency/
Visit this user's website Find all posts by this user
Quote this message in a reply
Post Reply 


Forum Jump:


User(s) browsing this thread: 2 Guest(s)