[tor-bugs] #2543 [Metrics]: Create graphs of #1919 torperfs

[Tor Bug Tracker & Wiki]

#2543: Create graphs of #1919 torperfs
----------------------------+-----------------------------------------------
    Reporter:  mikeperry    |       Owner:  karsten
        Type:  enhancement  |      Status:  closed 
    Priority:  normal       |   Milestone:         
   Component:  Metrics      |     Version:         
  Resolution:  implemented  |    Keywords:         
      Parent:               |      Points:         
Actualpoints:               |  
----------------------------+-----------------------------------------------
Changes (by karsten):

  * status:  new => closed
  * resolution:  => implemented


Comment:

 Replying to [comment:7 mikeperry]:
 > Yes, we can close this.

 Okay, closing.

 > I do think we should have these runs graphed on the metrics website in
 some form, possibly the same as what exists there now at
 https://metrics.torproject.org/performance.html, but with all 15 options
 in a dropdown, not just the three.

 I don't think that adding 12 new graphs to the metrics website will do
 what you want.  The current graphs have the purpose of comparing Torperf
 results over time.  The most useful Torperf graph right now is the one
 that combines the results from siv, moria, and ferrinii.  That's a single
 graph telling you the story how Tor performance has evolved over time.
 (Or rather, three graphs for the three file sizes.)

 Now, adding 12 graphs for the custom guard node selections won't be useful
 without comparing them to each other.  So, if I added these 3x4 graphs to
 the website, you'd open 4 browsers, load a graph in each of them, and
 compare the four graphs.  We should really come up with something better
 than that.

 Also, it's more complicated than it probably seems to add these new graphs
 without breaking the existing graphs.

 My plan is to do the analysis offline and not touch the website code at
 all.  If we find out that we like certain graphs and if we decide we want
 to track these graphs over time, then we should add new graphs to the
 website.  But I'm not even convinced that we'll keep the Torperfs with
 custom guard node selections running in the future.  It might be that
 we'll learn something from the experiment and decide we want to do a new
 experiment.  In that case we'll be angry about wasting programming effort
 to get new graphs on the website.

 > I also think we should capture the 1st and 4th quartiles in a different
 color, so we can keep an eye on the total spread over time (since variance
 is the pain point of tor use).

 I don't understand.  The 1st quartile is the area below the dark line and
 the 3rd quartile is the area above it.  What do you mean?

 > Does this sound right? Should this be two new tickets, or just one?

 Adding more graphs to the website shouldn't be a new ticket.  Not sure
 what you mean with the color thing, but that would be a new ticket.

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