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
  • Activity
  • Create a new issue
  • Issue Boards
Collapse sidebar

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

Closed
Open
Opened Jul 13, 2011 by Runa Sandvik@runa

Estimate cost of running a bridge in the cloud

Karsten and I talked about estimating the cost for running a bridge in the Amazon cloud. By estimating the cost of running a bridge in the cloud, we can come up with reasonable defaults for bandwidth limits etc.

Karsten did a quick analysis of the bandwidth consumed by bridges in June 2011 (see the attached pdf).

The first graph shows the total read and written GiB per month, focusing on the 10% of bridges with highest bandwidth consumption. Consider this graph the worst-case scenario from an operator's POV. The graph says, for example, that 1% of bridges read and wrote more than 100 GiB per month and that no bridge read and wrote more than 1 TiB.

The second graph looks at per-second bandwidth in KiB. In contrast to the first graph, the second graph only looks at intervals when the bridge was online. This graph says, for example, that the top 1% of bridges read and wrote more than 25 KiB per second and that no bridge read and wrote more than 225 KiB per second.

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