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

Closed (moved)
Open
Opened Jun 17, 2010 by Karsten Loesing@karsten

Identify reason for low dirreq-v3-shares in May and June 2010

The directory mirrors trusted, blutmagie, and vallenator all report very low dirreq-v3-share values in their extra-info descriptors since late May 2010 (see here).

We were able to identify the introduction of bandwidth-weight values in consensuses as cause for these low directory request shares. See the graph in the attachment. The more consensuses on a given day contain bandwidth-weights (up to 24), the lower are the reported dirreq-v3-shares.

A fix is suggested in #1564 (moved). In addition to that, we should calculate shares from descriptors archives rather than believing in what relays say.

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