Skip to content

GitLab

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

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.

  • The Tor Project
  • Metrics
  • Analysis
  • Issues
  • #31439

Closed
Open
Opened Aug 17, 2019 by Iain Learmonth@irl

Identify poorly performing relays from historical OnionPerf data

This closes the loop on legacy/trac#31435 (moved) to help us validate that the poorly performing relays have indeed been excluded as we would hope, and then we can check that we're not excluding so much performance that it would degrade the experience for everyone.

This task does not depend on legacy/trac#31435 (moved) however and can be progressed independently.

Some questions to answer:

  1. Low hanging fruit: are there some trends we should be aware of before we dive into this data, for example are there some "peak hours" where things are slower, or do things get slower on weekdays/weekends.
  2. How much data do we have to look at to identify with some certainty that a relay is slow? (1 day, 1 week, 1 month, 1 year?)
  3. What is our metric for "poorly performing"?
To upload designs, you'll need to enable LFS and have an admin enable hashed storage. More information
Assignee
Assign to
None
Milestone
None
Assign milestone
Time tracking
None
Due date
None
Reference: tpo/metrics/analysis#31439