[tor-bugs] #33076 [Metrics/Analysis]: Graph onionperf and consensus information from Rob's experiments

Tor Bug Tracker & Wiki blackhole at torproject.org
Wed Feb 5 11:14:56 UTC 2020


#33076: Graph onionperf and consensus information from Rob's experiments
-------------------------------------------------+-------------------------
 Reporter:  mikeperry                            |          Owner:
                                                 |  metrics-team
     Type:  task                                 |         Status:
                                                 |  needs_review
 Priority:  Medium                               |      Milestone:
Component:  Metrics/Analysis                     |        Version:
 Severity:  Normal                               |     Resolution:
 Keywords:  metrics-team-roadmap-2020Q1, sbws-   |  Actual Points:  2
  roadmap                                        |
Parent ID:  #33121                               |         Points:
 Reviewer:                                       |        Sponsor:
-------------------------------------------------+-------------------------

Comment (by karsten):

 Regarding Objective 3.1 of the MOSS proposal, I'm afraid that the CDF-
 Relay-* graphs will be out of scope. We had to reduce the budget and were
 only able to include graphs based on OnionPerf measurements, not based on
 other Tor descriptors. We can (and should) plan to include CDF-Relay-*
 graphs in that tool in the future, but the coding will likely have to wait
 until we have funding for that part.

 To give you an idea why the CDF-Relay-* graphs are harder to add than the
 OnionPerf-based onces: we're parsing 1.9M of compressed OnionPerf data for
 the CDF-TTFB and CDF-DL graphs, but 841M compressed tor descriptors for
 the CDF-Relay-* graphs. Making the last PDF I attached above kept my local
 workstation (1T NVMe, 64G RAM) busy for over an hour.

 Regarding adding graphs to the metrics website, I don't think that we can
 add any CDFs there without making major changes to the underlying graphing
 engine. Again, to given an example, the uncompressed data that is graphed
 in the last PDF I attached has a size of 4.5G. This is way different from
 existing graphs on the metrics website. I think we're looking at a tool
 that developers will run locally with data downloaded from CollecTor, a
 local database, and enough CPU time and RAM available to chew on all the
 data.

 This all shouldn't stop us from exploring possible graphs that we might
 need in the future. And I can make graphs like the last PDF for occasions
 like the torflow/sbws transition. They will just not be part of the tool
 that we'll have available once the MOSS proposal is done.

 I'll move the torflow/sbws discussion over to #33077. If you have any
 requests for changing the graphs above, except for the votes graph, please
 comment on this ticket. And when you think we're done, please indicate
 that here, too. Thanks!

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


More information about the tor-bugs mailing list