Opened 5 years ago

Last modified 3 years ago

#16997 new enhancement

Gather and report metrics for the number of channels a relay is servicing.

Reported by: yawning Owned by:
Priority: Medium Milestone: Tor: unspecified
Component: Core Tor/Tor Version: Tor: unspecified
Severity: Normal Keywords: metrics tor-relay privcount-maybe
Cc: Actual Points:
Parent ID: Points: medium
Reviewer: Sponsor: SponsorQ-can


It would be really nice to have statistics on the min/max/average number of simultaneous channels (TCP/IP connections) a relay is servicing for a few reasons:

  • If we are to add per-channel padding like in #16861 (or something more aggressive like people discuss), we need this to figure out how much extra bandwidth a relay will use, and possibly for parameter tuning.
  • This information will be helpful in determining if someone can/should run a relay, given their environment (Eg: To figure out if their relay will end up underutilized/bad for the network due to NAT connection table/OS limitations).

I'm uncertain as to how coarse grained this will need to be, particularly for Guards. Bridges SHOULD NOT report this information.

Child Tickets

Change History (10)

comment:1 Changed 5 years ago by yawning

I could have sworn I filed something like this earlier the last time it came up (in the context of discussing how awful some home routers are), if I did, then feel free to dup one of them.

comment:2 Changed 5 years ago by nickm

Points: medium

comment:3 Changed 5 years ago by nickm

Milestone: Tor: 0.2.8.x-finalTor: 0.2.9.x-final

It is impossible that we will fix all 226 currently open 028 tickets before 028 releases. Time to move some out. This is my second pass through the "new" and tickets, looking for things to move to 0.2.9.

comment:4 Changed 5 years ago by isabela

Milestone: Tor: 0.2.9.x-finalTor: 0.2.???

tickets market to be removed from milestone 029

comment:5 Changed 4 years ago by teor

Milestone: Tor: 0.2.???Tor: 0.3.???

Milestone renamed

comment:6 Changed 4 years ago by nickm

Keywords: tor-03-unspecified-201612 added
Milestone: Tor: 0.3.???Tor: unspecified

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

comment:7 Changed 3 years ago by nickm

Keywords: tor-03-unspecified-201612 removed

Remove an old triaging keyword.

comment:8 Changed 3 years ago by dgoulet

Keywords: tor-core removed

The tor-core keyword doesn't really make sense now that we have "Core Tor/Tor" for component.

comment:9 Changed 3 years ago by nickm

Keywords: tor-relay privcount-maybe added
Severity: Normal

comment:10 Changed 3 years ago by nickm

Sponsor: SponsorQ-can
Note: See TracTickets for help on using tickets.