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

Closed (moved)
Open
Opened Nov 27, 2011 by Roger Dingledine@arma

Is round-robining between each TLS conn the optimal scheduling approach?

Right now when a relay has n conns that want to write, we write fairly between each of them.

But we could imagine other scheduling approaches, like weighting the attention we give each conn by its capacity in the consensus, or weighting the attention we give it by how many circuits we have on that conn.

We can even imagine more complex approaches, like adding up the ewma weights on each conn, or choosing the conn with the quietest circuit (ewma-wise), or others.

We should make patches for some of these options and get simulations going.

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