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
  • #1863

Closed (moved)
Open
Opened Aug 24, 2010 by Mike Perry@mikeperry

Relays should store observed bandwidth in state file

arma suggested I write a proposal for this, but I believe it is a flat out bug. When a relay goes down, it looses its 24 hour observed bandwidth window. For fast relays, this can be catastropic, as it takes weeks for them to regain their bandwidth due to our slow descriptor refresh interval. The slow descriptor refresh interval can be shortened, but that requires careful study to make sure we do not increase the descriptor load on clients.

If we just instead stored this info in the state file to survive crashes, high bandwidth relays would still spend a loooong time gathering bandwidth (and maybe this is a really good thing?), but will at least not have to restart when they die.

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