Skip to content
GitLab
  • Menu
Projects Groups Snippets
  • 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
  • #21210
Closed (moved) (moved)
Open
Created Jan 12, 2017 by Nick Mathewson@nickm🐻

Analyze, and maybe improve, consensus diff proposal

We should use stats to re-run our numbers on the consensus diff proposal (140), and see how much bandwidth we expect to save. We should consider the impact of this proposal alongside alternative or related proposals, such as ones that would cause clients to download the consensus less frequently.

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