Opened 15 months ago

Last modified 11 months ago

#31439 assigned task

Identify poorly performing relays from historical OnionPerf data

Reported by: irl Owned by: metrics-team
Priority: Medium Milestone:
Component: Metrics/Analysis Version:
Severity: Normal Keywords:
Cc: Actual Points:
Parent ID: Points:
Reviewer: Sponsor:


This closes the loop on #31435 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 #31435 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"?

Child Tickets

Change History (1)

comment:1 Changed 11 months ago by karsten

Owner: changed from karsten to metrics-team

Assigning to metrics-team, as I'm not currently working on this.

Note: See TracTickets for help on using tickets.