Skip to content

GitLab

  • Menu
Projects Groups Snippets
    • Loading...
  • Help
    • Help
    • Support
    • Community forum
    • Submit feedback
    • Contribute to GitLab
  • Sign in
  • Trac Trac
  • Project information
    • Project information
    • Activity
    • Labels
    • Members
  • Issues 246
    • Issues 246
    • List
    • Boards
    • Service Desk
    • Milestones
  • Monitor
    • Monitor
    • Metrics
    • Incidents
  • Analytics
    • Analytics
    • Value stream
  • Wiki
    • Wiki
  • Activity
  • Create a new issue
  • Issue Boards
Collapse sidebar
  • Legacy
  • TracTrac
  • Issues
  • #25896

Closed (moved)
(moved)
Open
Created Apr 23, 2018 by Karsten Loesing@karsten

Move Fraction of connections used uni-/bidirectionally graph from Performance to Traffic category

While working on Sponsor 13 deliverable 2 I noticed that the Fraction of connections used uni-/bidirectionally graph would better fit into the Traffic category rather than the Performance category it's currently in.

Both categories are related. But my understanding of the Traffic category is that we're looking at statistics on the traffic in the Tor network that is generated by users and relayed by servers.

On the other hand, the Performance category is for statistics on performance measurements that we're doing specifically for the purpose of measuring the Tor network.

After moving the graph, all graphs in Traffic would be based on Tor descriptors, whereas all graphs in Performance would be based on Torperf/OnionPerf measurements. (In the future, we might add more graphs to the Performance category, which would also be based on OnionPerf measurements.)

I'll prepare a branch.

To upload designs, you'll need to enable LFS and have an admin enable hashed storage. More information
Assignee
Assign to
Time tracking