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

Closed (moved)
Open
Opened Jul 01, 2010 by Karsten Loesing@karsten

Calculate request share from descriptor archives rather than believing in what relays say

When estimating the number of recurring daily users, we divide the number of locally observed requests by the expected share of requests seen at that directory. The result is the estimated number of total requests in the network. Right now, we're using self-reported request shares for this calculation, but these numbers may be wrong. Only recently in May and June 2010, the directories report very low shares of 1/10 of the usual shares or even 0.0%, which must be wrong. Rather than believing the relays here, we could determine request shares that directories should see from the descriptor archives. The descriptor archives reveal how many directory mirrors there are and what bandwidths they advertise that are used for load balancing by clients. The request share of one of the directories is its bandwidth divided by the bandwidth of all directories.

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