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

Closed (moved)
Open
Opened Dec 09, 2011 by Karsten Loesing@karsten

Deal with 'double door' effects because our read and write rate limiting are independent

In sponsor F deliverable 2 we promised to "build and execute a plan for proposal 182" and to "figure out how it does or does not relate to the N23 congestion control design, to Ian's ideas about Defenestrator, etc."

There are a couple of subtasks to work on here:

  • Review proposal 182 and reword any unclear parts.

  • Review any existing patches for proposal 182 and update them for merging them into master.

  • Run simulations of proposal 182 using ExperimenTor and Shadow.

  • Make a list of designs that are related to proposal 182.

  • Compare proposal 182 to related designs.

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