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

Closed (moved)
Open
Opened Oct 01, 2017 by Roger Dingledine@arma

Somebody should profile a Tor 0.3.1.7 relay

moria1, running git master, seems to be using twice as much cpu or more as it used to use.

We hear stories on tor-relays of people whose rpi's are melting when they didn't used to melt.

I just talked to a person on #tor whose Windows 0.3.1.7 relay goes to 100% cpu and stays there.

I think something changed in cpu use between 0.3.0 and 0.3.1. We should try to figure out what it is and do something to make it better.

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