[tor-bugs] #1991 [Metrics]: Recognize poor guard performance and switch?

[Tor Bug Tracker & Wiki]

#1991: Recognize poor guard performance and switch?
-------------------------+--------------------------------------------------
 Reporter:  arma         |          Owner:          
     Type:  enhancement  |         Status:  assigned
 Priority:  normal       |      Milestone:          
Component:  Metrics      |        Version:          
 Keywords:               |         Parent:          
   Points:               |   Actualpoints:          
-------------------------+--------------------------------------------------
Changes (by karsten):

  * owner:  karsten =>
  * status:  new => assigned


Comment:

 Replying to [comment:3 arma]:
 > Now that we have some torperf path data: can we plot the torperf result
 (y axis) vs guard bandwidth weight in consensus at the time (x axis) and
 see if half the guards are ugly or just the really slow ones?

 Yes, we should be able to answer this question.  Here are the necessary
 steps to do so:

  - Wait for the `consolidate_stats.py` script to work again.  The version
 in Mike's branch ticket2618 should work, but waiting for #2672 to be
 implemented is probably smarter.
  - Extract consensus bandwidths of all relays and write them to a CSV
 file.  It's probably easiest for me to run an SQL query on the metrics
 database, like `SELECT validafter, fingerprint, bandwidth FROM
 statusentry`.
  - Merge the `.mergedata` file with the consensus bandwidth file to have a
 single CSV file that contains Torperf completion times and Guard node
 consensus bandwidths.
  - Make a scatter plot for a single such file, or concatenate multiple
 files with qualifiers and make a matrix of scatter plots.

 Unassigning this ticket, so that people (including me at a later time) can
 grab it.

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