Opened 6 years ago

Last modified 2 years ago

#9662 assigned defect

Make ntor handshake faster

Reported by: nickm Owned by: yawning
Priority: Medium Milestone: Tor: unspecified
Component: Core Tor/Tor Version:
Severity: Normal Keywords: tor-relay, performance, ntor, SponsorU-deferred, cpu
Cc: Actual Points:
Parent ID: Points: large
Reviewer: Sponsor:

Description

This is a parent ticket to cover performance improvements to ntor. It does not cover replacing ntor with a faster handshake.

Child Tickets

TicketStatusOwnerSummaryComponent
#8897needs_revisionFaster curve25519 implementation for ntorCore Tor/Tor
#9663closedTable-based basepoint multiply optimizations for ntor handshakeCore Tor/Tor
#9664needs_revisionPrecompute ephemeral keypairs for ntorCore Tor/Tor
#9667closedConsider batch-exponentiation tricks to improve ntor performanceCore Tor/Tor
#9719closedReuse Y in ntorCore Tor/Tor

Change History (23)

comment:1 Changed 6 years ago by nickm

Parent ID: #9657

comment:2 Changed 5 years ago by andrea

Milestone: Tor: 0.2.5.x-finalTor: 0.2.6.x-final

Moving this to 0.2.6 because some of the children won't be done for 0.2.5.

comment:3 Changed 5 years ago by nickm

Milestone: Tor: 0.2.6.x-finalTor: 0.2.???

Moving this to 0.2.??? since some of its items have been deferred out of 0.2.6. (Some are still in, though)

comment:4 Changed 5 years ago by nickm

This actually might not be worthwhile: see my comment on #8897. If I'm reading profiles right, it looks like we simply aren't spending our time in curve25519 right now. Even by the most generous profiling assumptions, we probably wouldn't have more than a percent or two of our time in curve25519 even if all of our handshakes were ntor.

comment:5 Changed 4 years ago by nickm

Milestone: Tor: 0.2.???Tor: 0.2.7.x-final

These may be worth looking at for 0.2.7.

comment:6 Changed 4 years ago by nickm

Status: newassigned

comment:7 Changed 4 years ago by nickm

Keywords: 027-triaged-1-in added

Marking some tickets as triaged-in for 0.2.7 based on early triage

comment:8 Changed 4 years ago by nickm

Milestone: Tor: 0.2.7.x-finalTor: 0.2.8.x-final

comment:9 Changed 4 years ago by nickm

Milestone: Tor: 0.2.8.x-finalTor: 0.2.???

These

comment:10 Changed 4 years ago by nickm

Milestone: Tor: 0.2.???Tor: 0.2.8.x-final
Owner: set to yawning
Sponsor: SponsorU

comment:11 Changed 4 years ago by nickm

Points: large

comment:12 Changed 3 years ago by nickm

Milestone: Tor: 0.2.8.x-finalTor: 0.2.9.x-final

These seem like features, or like other stuff unlikely to be possible this month. Bumping them to 0.2.9

comment:13 Changed 3 years ago by isabela

Sponsor: SponsorUSponsorU-can

comment:14 Changed 3 years ago by isabela

Milestone: Tor: 0.2.9.x-finalTor: 0.2.???

tickets market to be removed from milestone 029

comment:15 Changed 3 years ago by nickm

Keywords: SponsorU-deferred added
Sponsor: SponsorU-can

Remove the SponsorU status from these items, which we already decided to defer from 0.2.9. add the SponsorU-deferred tag instead in case we ever want to remember which ones these were.

comment:16 Changed 3 years ago by teor

Milestone: Tor: 0.2.???Tor: 0.3.???

Milestone renamed

comment:17 Changed 3 years ago by nickm

Keywords: tor-03-unspecified-201612 added
Milestone: Tor: 0.3.???Tor: unspecified

Finally admitting that 0.3.??? was a euphemism for Tor: unspecified all along.

comment:18 Changed 2 years ago by nickm

Parent ID: #9657
Severity: Normal

comment:19 Changed 2 years ago by nickm

Keywords: tor-03-unspecified-201612 removed

Remove an old triaging keyword.

comment:20 Changed 2 years ago by nickm

Keywords: 027-triaged-in added

comment:21 Changed 2 years ago by nickm

Keywords: 027-triaged-in removed

comment:22 Changed 2 years ago by nickm

Keywords: 027-triaged-1-in removed

comment:23 Changed 2 years ago by nickm

Keywords: cpu added
Note: See TracTickets for help on using tickets.