[Author Prev][Author Next][Thread Prev][Thread Next][Author Index][Thread Index]

Re: [tor-bugs] #13709 [Metrics Website]: Track some Dir Auth network stats

#13709: Track some Dir Auth network stats
---------------------------------+----------------------
     Reporter:  grarpamp         |      Owner:
         Type:  enhancement      |     Status:  reopened
     Priority:  normal           |  Milestone:
    Component:  Metrics Website  |    Version:
   Resolution:                   |   Keywords:
Actual Points:                   |  Parent ID:
       Points:                   |
---------------------------------+----------------------
Changes (by grarpamp):

 * status:  closed => reopened
 * resolution:  fixed =>


Comment:

 I'll restate another way in one sentence...
 Graph the bandwidth [etc] used by the specific subclass of the roughly 10
 bootstrap dir auths.

 You can't do it today because AFAIK dirbytes does not specifically track
 the unique bootstrap function of that set of 10 hosts. As you state,
 dirbytes is composed of both 'auths and mirrors'. AFAIK, mirrors do not
 carry bootstrap load past the consensus expiry, if at all. Only auths do
 that. So the real stats for that function are today unavailably buried
 beneath a single 'dirbytes' graph.

 People who want to run parallel tor protocol nets need the auth bandwidth
 data so they know how much to buy/locate to support their nets at any
 given scale. They don't care about mirror bandwidth since mirrors come
 from the user community, not the auth group. [TPO's relation to the
 current auth group is of no importance here. That there can be more than
 one tor protocol net in operation is.]

 I've no more to add.

--
Ticket URL: <https://trac.torproject.org/projects/tor/ticket/13709#comment:6>
Tor Bug Tracker & Wiki <https://trac.torproject.org/>
The Tor Project: anonymity online
_______________________________________________
tor-bugs mailing list
tor-bugs@xxxxxxxxxxxxxxxxxxxx
https://lists.torproject.org/cgi-bin/mailman/listinfo/tor-bugs