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

Closed (moved)
(moved)
Open
Created Apr 12, 2019 by Mike Perry@mikeperry

Ensure circuit padding can be safely disabled from consensus

Right now, to "disable" circuit padding, we have to set consensus parameters circpad_global_allowed_cells=1 and circpad_global_max_padding_pct=1, which actually only sets a limit of 1% of our traffic to be padding. Additionally, each padding cell that is not sent because this limit is reached causes an info log line to be written.

We need another way to fully disable padding, for A/B performance testing. And we should rate limit that info log so relays logging at info don't print a line for every single padding cell they don't send.

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