Skip to content
GitLab
Projects Groups Snippets
  • /
  • Help
    • Help
    • Support
    • Community forum
    • Submit feedback
    • Contribute to GitLab
  • Sign in
  • Tor Tor
  • Project information
    • Project information
    • Activity
    • Labels
    • Members
  • Repository
    • Repository
    • Files
    • Commits
    • Branches
    • Tags
    • Contributors
    • Graph
    • Compare
  • Issues 330
    • Issues 330
    • List
    • Boards
    • Service Desk
    • Milestones
  • Merge requests 31
    • Merge requests 31
  • CI/CD
    • CI/CD
    • Pipelines
    • Jobs
    • Schedules
  • Deployments
    • Deployments
    • Environments
    • Releases
  • Monitor
    • Monitor
    • Incidents
  • Analytics
    • Analytics
    • Value stream
    • CI/CD
    • Repository
  • Activity
  • Graph
  • Create a new issue
  • Jobs
  • Commits
  • Issue Boards
Collapse sidebar
  • The Tor Project
  • Core
  • TorTor
  • Issues
  • #29231
Closed
Open
Issue created Jan 30, 2019 by Roger Dingledine@armaReporter

Relays vastly underreport write-total in padding-counts line in extrainfo descriptor

Here is a snippet from WhatsGoingOn's extrainfo descriptor:

write-history 2019-01-27 18:10:06 (86400 s) 7709989888,6911394816,6582383616,7393989632,6065009664
read-history 2019-01-27 18:10:06 (86400 s) 7644498944,6824735744,6550761472,7355173888,6059125760
[...]
padding-counts 2019-01-27 22:06:23 (86400 s) bin-size=10000 write-drop=0 write-pad=220000 write-total=250000 read-drop=0 read-pad=210000 read-total=12310000 enabled-read-pad=10000 enabled-read-total=20000 enabled-write-pad=10000 enabled-write-total=10000 max-chanpad-timers=6

Notice how the read-total is reasonable compared to read-history, but the write-total is way undercounting compared to write-history.

I suspect that write-total is the wrong one.

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