Opened 7 years ago

Closed 3 years ago

#9320 closed task (wontfix)

Assign bandwidth to new relays faster

Reported by: hsn Owned by:
Priority: Medium Milestone: Tor: unspecified
Component: Core Tor/Tor Version:
Severity: Normal Keywords:
Cc: Actual Points:
Parent ID: Points:
Reviewer: Sponsor:

Description

Tor is very unfriendly to short time running relays. It takes too much time until relay starts to pull some real workload. Currently there is no point in running relay for short time (few hours) and maintaining long uptime (as few restarts as possible) is critical for getting bw assigned by authorities.

example: fresh new relay with 1d4h uptime and 100mbit bw gets assigned too little bw wieght (around 350KB/s) and even with that, it gets in first day about 400 MB of traffic in each direction. It takes about 6 hours until bw of new relay get measured and even after that, it gets assigned very little % of its real weight.

This is topic "why i get so little bw" is often asked on IRC.

look at tor status - http://torstatus.blutmagie.de/index.php?SR=Uptime&SO=Desc about 1/4 of relays has < 1 day uptime. It would be good to make their available bw really used.

Child Tickets

Change History (5)

comment:1 Changed 7 years ago by nickm

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

comment:2 Changed 4 years ago by teor

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

Milestone renamed

comment:3 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:4 Changed 3 years ago by nickm

Keywords: tor-03-unspecified-201612 removed

Remove an old triaging keyword.

comment:5 Changed 3 years ago by nickm

Resolution: wontfix
Severity: Normal
Status: newclosed

Closing as "wontfix", not because this is a bad idea, but because if it happens, it's got to happen as part of a better bandwidth measurement architecture. The existing bwauth code is (I'm told) held together with duct tape, good intentions, and muttered profanities.

Note: See TracTickets for help on using tickets.