Overhead when started, but no functions enabled about clumsy

[jagt]

Hi mlinnell, thanks for your detailed report. Let me explain what I know about this:

clumsy does introduce overhead when it starts filtering. All packets will be captured and resend and it would definitely introduce overhead. I'm suppose it would be quite significant as we've intercept what should be done directly by the OS. When you've set the lag to 20ms, clumsy would further hold the packets a little bit longer. Let's assume the lag introduced by clumsy is like 40ms in your settings.

The first thing to notice is that in the filtering, you've included both inbound and outbound packets, this might doubled the latency. Then clumsy introduced is happening on per network packet, not per HTTP request. For example when a TCP connection is established, it needs three packets to establish the connection. Every packets sent is having a 40ms lag, then when the TCP connection get established it's already 40_3_2 = 240ms delay. Then for a web page to be DOM ready, some requests needs to be done synchronized, ie in a particular order. Say we have three requests that needs to be get in order, then the delay triples to 240*3 = 720ms.

This is quite back of the envelope calculation, the gist is that you can't treat the parameters in clumsy as an accurate measure (in other words I'm not good enough to make it accurate 😄 ). It guarantee the enabled functions would happen and the parameters are used to control it. You shouldn't take the numbers in clumsy seriously.

Hope this helps. I'll update this to the manual page later. Thanks again for your feedback.

(edited: fix the wrong calculations)