[tor-bugs] #6498 [Metrics Website]: new metrics graph showing number of 100mbit exits

[Tor Bug Tracker & Wiki]

#6498: new metrics graph showing number of 100mbit exits
-----------------------------+----------------------------------------------
 Reporter:  arma             |          Owner:     
     Type:  enhancement      |         Status:  new
 Priority:  normal           |      Milestone:     
Component:  Metrics Website  |        Version:     
 Keywords:                   |         Parent:     
   Points:                   |   Actualpoints:     
-----------------------------+----------------------------------------------

Comment(by karsten):

 Replying to [ticket:6498 arma]:
 > For the exit sponsoring plan, it would be good to make a periodic (e.g.
 daily) list of 100mbit+ exits. Specifically, these would be relays where:
 >
 > - Their bandwidth rate is at least 12500KB
 > - Their advertised bandwidth is above some cutoff, say 5000KB.
 > - Their exit policy allows at least 80, 443, 554, and 1755.
 >
 > If we sorted this list by consensus weight, showing percentage of exit
 weights they are and providing links to atlas or some other individual
 page for each, we'd be doing even better.

 By "periodic", do you mean updating that list periodically, or keeping
 lists of all past periods and letting users navigate between them?  I have
 an idea for building the former, but not for the latter.  Assuming you
 mean a single list of current 100mbit+ exits in the following.

 How about we extend Atlas itself for this?  It's the better fit than the
 metrics website, because it was specifically designed for displaying
 individual relay information vs. aggregated statistics.

 The way how the extended Atlas would work is that you select a "stored
 query" of some sort instead of searching by nickname/fingerprint/address.
 Atlas would make sure that the three criteria you mentioned are included
 in the filter, and it would sort by consensus weight and show percentage
 of exit weights.  And of course, if you click on a relay, you'd get the
 already known details page for that relay.  In the near future, that
 details page might contain a graph with exit weight percentage over time.

 The only downside of that plan is that it may take weeks until
 everything's implemented, and you probably want to have it really soon.
 That problem shouldn't prevent us from extending Atlas, because it's the
 better design IMO.  But I can easily hack up a Python script that outputs
 the requested information.  We could even run it in a daily cronjob and
 send its results to the tor-relays mailing list.  We can shut it down once
 Atlas is ready.

 > Then we could imagine doing a graph over time of the number of relays in
 this list. Ideally we will be able to see it go up. :)

 This is something for the metrics website.  I'll make a sample graph later
 today or tomorrow and attach it here.

 > (I'm not quite sure what the advertised bandwidth cutoff should be.
 Ideally it would be quite high, except there might come a time where we
 have such excess capacity that some relays don't see enormous spikes. If
 they have the capacity, it's a *feature* that they don't see the spikes.
 So maybe we should pick a low cutoff to be flexible for the future.)

 The suggested solution above would allow you to tweak the advertised
 bandwidth parameter in Atlas.  Changing that parameter for the metrics
 website graph will be somewhat harder, but not impossible.

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