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

Closed (moved)
Open
Opened Jul 31, 2012 by Roger Dingledine@arma

new metrics graph showing number of 100mbit exits

For the exit sponsoring plan, it would be good to make a periodic (e.g. daily) list of 100mbit+ exits. Specifically, these would be relays where:

  • Their bandwidth rate is at least 12500KB
  • Their advertised bandwidth is above some cutoff, say 5000KB.
  • Their exit policy allows at least 80, 443, 554, and 1755.

If we sorted this list by consensus weight, showing percentage of exit weights they are and providing links to atlas or some other individual page for each, we'd be doing even better.

Then we could imagine doing a graph over time of the number of relays in this list. Ideally we will be able to see it go up. :)

(I'm not quite sure what the advertised bandwidth cutoff should be. Ideally it would be quite high, except there might come a time where we have such excess capacity that some relays don't see enormous spikes. If they have the capacity, it's a feature that they don't see the spikes. So maybe we should pick a low cutoff to be flexible for the future.)

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