Opened 8 years ago

Last modified 2 years ago

#5271 new enhancement

add log messages when a hidden service consistently doesn't have any preemptive circuit ready

Reported by: arma Owned by:
Priority: Very Low Milestone: Tor: unspecified
Component: Core Tor/Tor Version:
Severity: Normal Keywords: tor-hs, intro, performance, analysis
Cc: dgoulet, asn Actual Points:
Parent ID: Points: small
Reviewer: Sponsor:

Description

We basically just made up numbers for how many preemptive circuits a hidden service should have. Are popular hidden services mis-tuned?

A first step to answering this question might be to teach Tors to notice if they are too often needing to build a new circuit on the spot. They could log when it happens, and the operators could let us know they see the log and encourage us to make these parameters into config options.

Unless there's a better way to get started?

Child Tickets

TicketTypeStatusOwnerSummary
#13239defectclosedMaybe we want three preemptive internal circs for hidden services?

Change History (7)

comment:1 Changed 7 years ago by nickm

Keywords: tor-hs added

comment:2 Changed 7 years ago by nickm

Component: Tor Hidden ServicesTor

comment:3 Changed 4 years ago by dgoulet

Keywords: intro added
Milestone: Tor: unspecifiedTor: 0.2.???
Points: small
Priority: MediumVery Low
Severity: Normal

comment:4 Changed 3 years ago by teor

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

Milestone renamed

comment:5 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:6 Changed 2 years ago by nickm

Keywords: tor-03-unspecified-201612 removed

Remove an old triaging keyword.

comment:7 Changed 2 years ago by nickm

Cc: dgoulet asn added
Keywords: performance analysis added
Note: See TracTickets for help on using tickets.