Opened 21 months ago

Closed 4 months ago

#17170 closed enhancement (implemented)

documenation for BandwidthRate etc should mention TCP/IP overhead not included

Reported by: starlight Owned by:
Priority: Low Milestone: Tor: 0.3.1.x-final
Component: Core Tor/Tor Version:
Severity: Normal Keywords: docs, tor-03-unspecified-201612
Cc: Actual Points:
Parent ID: Points: small
Reviewer: Sponsor:

Description

The Tor manual page should mention that
BandwidthRate, BandwidthBurst, etc control
only application layer byte rates and that
TCP/IP overhead adds approximately 17%
to the total, or stated a different way
the payload data rate is about 15% of
total traffic.

Is easy to overlook this important
detail and it matters greatly when one is
configuring maximums in order to stay
within ISP bandwidth allocations. ISPs
count total traffic and over-limit charges
can be extortionist. Is unpleasant
to exceed them by accident.

The overhead accounting also matters if one
is setting BandwidthRate for an unmetered
Internet connection with the idea of
minimizing TCP/IP congestion in preference
to Tor router flow control.

Generally ISPs do not charge for MAC layer
bytes which are not carried on WAN links
and so the above estimates omit it.

Child Tickets

Change History (7)

comment:1 Changed 21 months ago by teor

  • Keywords docs added
  • Milestone set to Tor: 0.2.8.x-final

comment:2 Changed 21 months ago by teor

  • Points set to small

comment:3 Changed 21 months ago by teor

  • Status changed from new to needs_information

This change should also note that DNS traffic from Exits is not included in the total. We are trying to find out the typical fraction of DNS traffic in exit traffic.

comment:4 Changed 18 months ago by nickm

  • Milestone changed from Tor: 0.2.8.x-final to Tor: 0.2.???

Move a bunch of (but not all) low-priority items to 0.2.???. If you write a patch, it can still get into 0.2.8

comment:5 Changed 8 months ago by teor

  • Milestone changed from Tor: 0.2.??? to Tor: 0.3.???

Milestone renamed

comment:6 Changed 6 months ago by nickm

  • Keywords tor-03-unspecified-201612 added
  • Milestone changed from Tor: 0.3.??? to Tor: unspecified

Finally admitting that 0.3.??? was a euphemism for Tor: unspecified all along.

comment:7 Changed 4 months ago by nickm

  • Milestone changed from Tor: unspecified to Tor: 0.3.1.x-final
  • Resolution set to implemented
  • Severity set to Normal
  • Status changed from needs_information to closed

Resolved in 8083e7c80bb2ef. (It was easier to resolve it than to do anything else with the ticket.)

Note: See TracTickets for help on using tickets.