Opened 7 years ago

Closed 7 years ago

#6671 closed enhancement (implemented)

network advertised bandwidth/history graph by Exit / Guard flag?

Reported by: arma Owned by: karsten
Priority: Medium Milestone:
Component: Metrics/Website Version:
Severity: Keywords:
Cc: mo, karsten Actual Points:
Parent ID: Points:
Reviewer: Sponsor:

Description

https://metrics.torproject.org/network.html#bandwidth is great but doesn't let me see the trends for the nodes with the Exit flag (or with the Guard flag).

(I can't do it with https://metrics.torproject.org/network.html#bwhist-flags because a) that's only bandwidth history, not advertised bandwidth, and b) it doesn't given me the sum of Exit flags or the sum of Guard flags. And https://metrics.torproject.org/network.html#relayflags is totally what I want but it gives number-of-relays, not either bandwidth metric.)

Child Tickets

Attachments (2)

bandwidth-flags.png (41.2 KB) - added by karsten 7 years ago.
bandwidth-flags-2012-08-28.png (39.5 KB) - added by karsten 7 years ago.

Download all attachments as: .zip

Change History (9)

comment:1 Changed 7 years ago by arma

Cc: karsten added

comment:2 Changed 7 years ago by karsten

So, you want https://metrics.torproject.org/network.html#bwhist-flags, but with

  • graph title "Advertised bandwidth by relay flags" and
  • two lines "Exit (and maybe Guard)" and "Guard (and maybe Exit)"?

If so, that sounds doable.

comment:3 Changed 7 years ago by arma

Yes, for starters.

Also missing are lines for bandwidth history for those two cases.

Would all four lines fit on a graph adequately? In that case it would be more like https://metrics.torproject.org/network.html#bandwidth but with two lines for Guard (and maybe Exit) and two lines for Exit (and maybe Guard).

Changed 7 years ago by karsten

Attachment: bandwidth-flags.png added

comment:4 Changed 7 years ago by karsten

Owner: set to karsten
Status: newaccepted

Replying to arma:

Yes, for starters.

Also missing are lines for bandwidth history for those two cases.

Ah, I missed the word "history". Yes, that's easy. We already have that data.

Would all four lines fit on a graph adequately? In that case it would be more like https://metrics.torproject.org/network.html#bandwidth but with two lines for Guard (and maybe Exit) and two lines for Exit (and maybe Guard).

Putting all lines on one graph might be too much, but we can split the graph into two, similar to what we did with the almost-fast-exits graph. I quickly wrote some database code for an example. I also added a Running line for comparison, and I left out the "(and maybe $flag)" part to be consistent with the relay-number-by-flags graph. If you like this graph, I'll clean up the code and deploy it on the metrics website.

Changed 7 years ago by karsten

comment:5 Changed 7 years ago by karsten

Status: acceptedneeds_information

Here's a second graph, this time showing advertised bandwidth and bandwidth history on a single y axis. I also tried varying line types, but didn't like the result at all.

We could add check boxes to the website and disable the Running lines by default. That would reduce the (default) number of lines in the graph to four.

Is this what you had in mind?

comment:6 Changed 7 years ago by arma

the graph looks really cluttered with the six lines, you're right.

I think it would look fine with the four lines though.

Also, we might try to sort the items in the legend by what order the lines are in the graph.

Thanks!

comment:7 Changed 7 years ago by karsten

Resolution: implemented
Status: needs_informationclosed

After some fighting with R, I removed the Running lines. Here's the result. I also re-ordered the items in the legend, but it's static and won't change when the lines in the graph change. But it should be somewhat more intuitive in this order.

I think this concludes the ticket. Optimistically closing. If there's something else, please re-open.

Note: See TracTickets for help on using tickets.