Skip to content

GitLab

  • Menu
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 823
    • Issues 823
    • 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
  • #9709
Closed
Open
Created Sep 09, 2013 by Roger Dingledine@armaReporter

We accept way more tap cells than we process

Our fix in legacy/trac#7291 (moved) was meant to have us turn away onionskins that we're unlikely to get to. But in practice our legacy/trac#9658 (moved) patch shows that we're accepting way more than we process.

Linus briefly did a test where he cherry-picked the legacy/trac#9658 (moved) patch onto 0.2.4.16-rc and it was still only handling about 25% of incoming requests. His cursory analysis was that he was dropping them with the

    log_info(LD_CIRC,
             "Circuit create request is too old; canceling due to overload.");

line.

Should we be refusing these earlier, so clients can know to go elsewhere?

One possible culprit is that the main Tor thread is too busy to give cpuworker events out on time.

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