[tor-bugs] #13209 [Analysis]: Write a hidden service hsdir health measurer

[Tor Bug Tracker & Wiki]

#13209: Write a hidden service hsdir health measurer
--------------------------+------------------------------------------------
     Reporter:  arma      |      Owner:
         Type:  project   |     Status:  assigned
     Priority:  major     |  Milestone:  Tor: 0.2.7.x-final
    Component:  Analysis  |    Version:  Tor: 0.2.7
   Resolution:            |   Keywords:  SponsorR, tor-hs, 027-triaged-1-in
Actual Points:            |  Parent ID:
       Points:            |
  medium/large            |
--------------------------+------------------------------------------------

Comment (by asn):

 I think the main question that remains to be answered here is #13208:

 - What's the average number of hsdir fetches before we get the hsdesc?

   That is, how many HSDirs will a client try on average before they
   manage to fetch the descriptor? If the answer is close to 1.0, it
   means that node churn does not affect the hash ring much (and in
   theory we could even decrease the number of HSDirs per HS).

 Since this is an experiment, it ''might'' make sense to have our HS
 health tool download consensuses like a normal client, instead of
 always using the latest one.

 If we wanted to learn the actual value here, we could do #15962 and
 actually measure the churn effect using historical metrics data.

--
Ticket URL: <https://trac.torproject.org/projects/tor/ticket/13209#comment:10>
Tor Bug Tracker & Wiki <https://trac.torproject.org/>
The Tor Project: anonymity online