Skip to content
GitLab
Projects Groups Snippets
  • /
  • Help
    • Help
    • Support
    • Community forum
    • Submit feedback
    • Contribute to GitLab
  • Sign in
  • Tor Tor
  • Project information
    • Project information
    • Activity
    • Labels
    • Members
  • Repository
    • Repository
    • Files
    • Commits
    • Branches
    • Tags
    • Contributors
    • Graph
    • Compare
  • Issues 325
    • Issues 325
    • List
    • Boards
    • Service Desk
    • Milestones
  • Merge requests 30
    • Merge requests 30
  • CI/CD
    • CI/CD
    • Pipelines
    • Jobs
    • Schedules
  • Deployments
    • Deployments
    • Environments
    • Releases
  • Monitor
    • Monitor
    • Incidents
  • Analytics
    • Analytics
    • Value stream
    • CI/CD
    • Repository
  • Activity
  • Graph
  • Create a new issue
  • Jobs
  • Commits
  • Issue Boards
Collapse sidebar
  • The Tor Project
  • Core
  • TorTor
  • Issues
  • #40214
Closed
Open
Issue created Dec 04, 2020 by Mike Perry@mikeperryDeveloper

Tune KIST and EWMA with Congestion Control

Once congestion control (Proposal 324) is implemented, we will need to re-visit our KIST and EWMA parameter choices and performance, as EWMA will provide better fairness properties by increasing RTT of overly loud circuits, which will cause congestion control to back off.

The KIST interval will also influence the number of circuits that can be involved in prioritization decisions. Larger intervals mean lower throughput, but more prioritization choice. Smaller intervals mean higher throughput, but less prioritization choice.

For some additional background on KIST tuning, see #29427 (closed).

To upload designs, you'll need to enable LFS and have an admin enable hashed storage. More information
Assignee
Assign to
Time tracking