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

Closed
Open
Opened Feb 07, 2012 by Roger Dingledine@arma

Measure obfsproxy/obfs2 performance

Once we get the client-side of #4927 (closed) (tbb + obfs) building, I wonder if we should seed it with a fast stable obfs2 bridge. That way you can use your own obfs2 bridge, but you can also try out obfs2 without needing to find your own.

Clearly, if the bundle becomes way popular, that bridge will get hammered in terms of bandwidth.

But will obfsproxy hold up until that point, on the bridge side? Or will it fall over earlier? Any guesses, or better, some way to find out for reals?

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#5038