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

Closed (moved)
Open
Opened Sep 04, 2013 by Nick Mathewson@nickm🐙

Precompute ephemeral keypairs for ntor

In the ntor handshake, on the server side, we need to generate a new y,Y pair for every handshake. But there's no reason this needs to happen on demand; instead, it could be lovely to do batches of them ahead of time, so that we can respond to requests faster. This wouldn't lower our CPU requirements when we were under load, but it might help us with circuit creation latency under less-than-horrible loads.

Before we go ahead and do this, it might be clever to verify that there are in fact times when cpuworkers are idle on busy servers.

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