Skip to content

GitLab

  • Projects
  • Groups
  • Snippets
  • Help
    • Loading...
  • Help
    • Help
    • Support
    • Community forum
    • Submit feedback
    • Contribute to GitLab
  • Sign in
Trac
Trac
  • Project overview
    • Project overview
    • Details
    • Activity
  • Issues 246
    • Issues 246
    • List
    • Boards
    • Labels
    • Service Desk
    • Milestones
  • Operations
    • Operations
    • Metrics
    • Incidents
  • Analytics
    • Analytics
    • Value Stream
  • Wiki
    • Wiki
  • Members
    • Members
  • Collapse sidebar
  • Activity
  • Create a new issue
  • Issue Boards

GitLab is used only for code review, issue tracking and project management. Canonical locations for source code are still https://gitweb.torproject.org/ https://git.torproject.org/ and git-rw.torproject.org.

  • Legacy
  • TracTrac
  • Issues
  • #21822

Closed (moved)
Open
Opened Mar 26, 2017 by Roger Dingledine@arma

atlas thinks kbytes are 1000 bytes, but relays think kbytes are 1024 bytes

Gurgle has this bandwidth line in its descriptor:

bandwidth 12582912 52428800 10079609

That 52428800 means that Ian wrote "50 MBytes" in his torrc file.

But Atlas, when you hover over the advertised bandwidth, says that Ian set his burst to 52.43MB/s.

It would seem that Atlas should divide by 1024*1024, rather than dividing by a million, when telling us the bandwidth numbers.

(Also, technically burst is measured in MB, not in MB/s.)

To upload designs, you'll need to enable LFS and have admin enable hashed storage. More information
Assignee
Assign to
None
Milestone
None
Assign milestone
Time tracking
None
Due date
None
Reference: legacy/trac#21822