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

Closed (moved)
Open
Opened May 01, 2012 by Roger Dingledine@arma

Don't make too many circuits once we're separating streams by domain

In #3455 (moved) we're heading toward a world where each Torbutton user has a separate circuit for each referer header. So rather than using the same circuit for an up-to-10-minute period, we could potentially be asking for way way more circuits. That's most bad because of the CPU load it will place on relays.

How many circuits is that exactly, for various client behaviors? We should instrument Tor clients to track how many circuits we would have made under various proposal-171 variations, to get a better handle on how concerned we should be.

Should we consider extending the 10-minute expiry time, to balance the growth in circuits?

Right now we abandon a circuit as soon as any stream takes 10 (or 15) seconds to hear its begin cell. How many circuits are we throwing away early in practice? That's another opportunity to reduce the pain here.

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