Skip to content
GitLab
Projects Groups Snippets
  • /
  • Help
    • Help
    • Support
    • Community forum
    • Submit feedback
    • Contribute to GitLab
  • Sign in
  • A Analysis
  • Project information
    • Project information
    • Activity
    • Labels
    • Members
  • Issues 6
    • Issues 6
    • List
    • Boards
    • Service Desk
    • Milestones
  • Monitor
    • Monitor
    • Incidents
  • Analytics
    • Analytics
    • Value stream
  • Activity
  • Create a new issue
  • Issue Boards
Collapse sidebar
  • The Tor Project
  • Network Health
  • Metrics
  • Analysis
  • Issues
  • #40008
Closed (moved) (moved)
Open
Issue created Nov 02, 2021 by Hiro@hiro🏄Owner

CDFs graphs for Exits and Guard+Exits, for simulated and live Tor network

We will need the following graphs:

    - CDFs for Exits and Guard+Exits
      - 'exit-kibibytes-read'+'exit-kibibytes-written'/'epoll_cnt' 
      - 'exit-kibibytes-read'+'exit-kibibytes-written'/'epoll_wait'

We can get this info from descriptor and shadow logs.

Furthermore we will also need the following graphs:

  - Graphs:
    - Utilization CDFs: graph for all relays, and one graph each for "Guard",
      "Exit", "Middle", "Guard+Exit"
      - take the bandwidth history from extra-info, and divide it by the advertized
        bandwidth from the descriptor.
        - In Shadow, we may have to use the Link capacity instead of adv bw,
          if clients don't burst enough in 1 sim period to get adv bw high
          enough

We also want a new baseline date range, for a flooding period.

For more details and prioritization, see #40008 (comment 2764299)

cc\ @mikeperry cc\ @jnewsome

Edited Dec 02, 2021 by Mike Perry
To upload designs, you'll need to enable LFS and have an admin enable hashed storage. More information
Assignee
Assign to
Time tracking