Clean up logic for requesting immediate acks
Opened 13 months ago
Last modified 12 months ago
#2705newenhancement
Clean up logic for requesting immediate acks
Reported by:Zlatin BalevskyOwned by: Priority: minor Milestone: undecided Component: streaming Version: 0.9.45 Keywords: testnet Cc:
Parent Tickets:
Sensitive: no
Description
The logic for when to request an immediate ack relies on what I call "alchemy" in the sense that it uses magic numbers and transmit window ratios.
I decided to test whether it makes any difference and if the code can be simplified. The attached spreadsheet lists the final speed readings as reported by eepget of 1MB file. The testnet is set up with 70ms delay between each link for 140ms RTT between any two nodes. The tunnels are ECIES, 0.9.45-0.
tl;dr: The current logic improves upon the case where immediate acks are never requested, but always requesting improves more. Note that even though the acks are called immediate, they're still delayed by 150ms.