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

Closed (moved)
(moved)
Open
Created May 08, 2015 by David Goulet@dgoulet🆘

Calculate HS churn effect using historical metrics data

From parent ticket #13209 (moved) in order to break it down a bit.

Lets look at the historical metrics data involving relay churn (easy to see in the consensus) and relay restarts (where uptime resets) and calculate what the answer ought to be. And if our prediction is much different from the reality, why?

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