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
  • Activity
  • Create a new issue
  • Issue Boards
Collapse sidebar

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

Closed (moved)
Open
Opened May 31, 2013 by Trac@tracbot

"Your computer is too slow" -> improving multithreading of "circuit creation requests"?

Hi,

I'm seeing some tor behavior we used to see in past I2P versions: new connections handling is quite hogging, probably because it is not really spreading its load on every cores available. I mean, CPU is globally almost only 33% used, but tor complains about it being too slow, and suggests lowering MaxAdvertisedBandwidth, which is finally "a waste".

I2P worked on this and now overall bandwith usage has dramatically increased, and CPU is better used.

Is there a way to improve the parallelism of "circuit creation" handling in tor?

Trac:
Username: elgo

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