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

Closed (moved)
Open
Opened Oct 16, 2015 by Roger Dingledine@arma

Track consensus fetch times per country?

Right now Tor directories track consensus download times, and put that in their extrainfo descriptors.

It would be useful to have this info broken down per country, so we can e.g. learn when vanilla Tor starts getting throttled in a particular country (like it did a few years ago). And hey, for obfs4 bridges, it would be neat to compare if they are able to deliver the consensus quickly when vanilla Tor isn't.

I don't think we should put per-country performance stats into extra-info descs here, mostly since they'd get too big. I also briefly considered saying "well I only care about these two countries, so let's put only those in the extrainfo descs", but I think that's not a great strategy either.

So I think the current goal for this ticket is to produce an easy patch for relay operators to use if they want to measure this data, and also to either make this patch sufficiently safe that we're ok if relay operators want to apply it -- or convince ourselves that it is too unsafe and it should not be used.

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#17366