Skip to content

GitLab

  • Projects
  • Groups
  • Snippets
  • Help
    • Loading...
  • Help
    • Help
    • Support
    • Community forum
    • Submit feedback
    • Contribute to GitLab
  • Sign in
Trac
Trac
  • Project overview
    • Project overview
    • Details
    • Activity
  • Issues 246
    • Issues 246
    • List
    • Boards
    • Labels
    • Service Desk
    • Milestones
  • Operations
    • Operations
    • Metrics
    • Incidents
  • Analytics
    • Analytics
    • Value Stream
  • Wiki
    • Wiki
  • Members
    • Members
  • Collapse sidebar
  • Activity
  • Create a new issue
  • Issue Boards

GitLab is used only for code review, issue tracking and project management. Canonical locations for source code are still https://gitweb.torproject.org/ https://git.torproject.org/ and git-rw.torproject.org.

  • Legacy
  • TracTrac
  • Issues
  • #13126

Closed (moved)
Open
Opened Sep 11, 2014 by George Kadianakis@asn

Deprecate smartlist_choose_node_by_bandwidth() ?

smartlist_choose_node_by_bandwidth() is a function that chooses a random node from a smartlist, weighted by the advertised bandwidth of each element.

It's the older sister of smartlist_choose_node_by_bandwidth_weights() (see node_sl_choose_by_bandwidth()) which uses advertised bandwidth instead of measured. Its algorithm is old and buggy (#13066 (moved)) and apparently documented at http://archives.seul.org/or/dev/Jul-2007/msg00056.html.

Now that Tor has measured bandwidth, we should make sure that the function is unused and then maybe consider deprecating it. However, we should make it so that we are still able to gracefully handle a situation where we don't have measured bandwidths or weights.

To upload designs, you'll need to enable LFS and have an admin enable hashed storage. More information
Assignee
Assign to
Tor: 0.2.6.x-final
Milestone
Tor: 0.2.6.x-final
Assign milestone
Time tracking
None
Due date
None
Reference: legacy/trac#13126