Hi!

Metrics Meetings are happening every Thursday at 15UTC in #tor-meeting in irc.oftc.net

Here are the minutes for the meeting of June 4rd:

http://meetbot.debian.net/tor-meeting/2020/tor-meeting.2020-06-04-15.00.log....

Meeting pad: https://pad.riseup.net/p/tor-metricsteam-2020.1-keep

And here is the pad notes:

----------------------------------------------------- Agenda Thursday, June 4th, 15 UTC -----------------------------------------------------

OnionPerf project: https://trac.torproject.org/projects/tor/wiki/org/sponsors/Sponsor59

Roadmap for June:

Roadmap draft: https://people.torproject.org/~karsten/volatile/scalability-and-performance-...

What tasks are we missing in this roadmap draft?

There are some tickets in Metrics/Cloud #33309->33313;#32725

Write some simple scripts to generate ID hexes of relays with certain properties as input for #33260.

What should we include in the roadmap for the 4 weeks in June from 2020-06-05 to 2020-07-02 with 2.5 points per week or 10.0 points total capacity?

Tickets that are almost done and that we can likely resolve quickly

Add CDF-DL graph (#33257), 0.2 points remaining +1+1+1

Fix message logging and filtering (#29369), 0.2 points remaining +1+1+1

Make -o/-i arguments mutually exclusive (#34316), 0.1 points remaining +1+1+1

Find out why onion service measurements have gotten slower (#34303), 0.1 points remaining +1+1+1

Analyze unusual distribution of time to extend to first hop in circuit (#34257), 0.4 points remaining +1+1+1

Add digests and sizes to index.xml (#29365), 0.2 points remaining +1+1+1

Add single onion service mode (#29368), 0.2 points remaining +1+1+1

Enhancements related to TGen and Shadow

Update OnionPerf to TGen 1.0.0 (#33974), 2.0 points remaining+1+1+1

Circuit build timeouts

Add CBT events to Onionperf result files (#33420), 0.7 points remaining +1

Include more events about CBT in results (#33422), 0.5 points remaining +1

Long-running measurement instances

Update metrics-web to only plot "official" data (#33397), 0.5 points remaining+1

Check OnionPerf instances from Nagios (#28271), 1.0 points remaining+1

Guards

Measure static guard nodes with OnionPerf (#33399), 1.9 points remaining +1+1

Track which Guard is used for experimental measurements (#33421), 3.0 points remaining +1+1

Measurement mode

Measure mode with arbitrary tgen traffic models (#29370), 0.9 points remaining +1+1

Multiple downloads for oneshot mode (#33432), 0.2 points remaining +1+1

What we're leaving for the next roadmap in July:

Enhancements related to TGen and Shadow

OnionPerf TGen parser needs reworking (#30362), 3.0 points remaining

Replace TorCtlParser with OnionTrace's control log parser (#34213), 2.0 points remaining

Long-running measurement instances

Add new metadata fields and definitions (#33391), 1.0 points remaining

Add new metadata fields to json output (#33392), 0.5 points remaining

Guards

Add analysis to support static guard measurements (#33419), 2.0 points remaining

Measurement mode

Develop and deploy tgen model resembling ping (#30798), 5.0 points remaining

TGen/Tor integration

Document and maybe improve how we're mapping TGen transfers to Tor streams/circuits (#34231), 1.0 points remaining

Visualization mode

Store measurements in a local database to reduce plotting time (#33259), 5.0 points remaining

Split PROXY errors into whatever reasons are given in TorCtl logs (#34218), 0.3 points remaining

Add option to filter graphed OnionPerf results by relay fingerprint (#33260), 3.0 points remaining

New suggestions from above:

There are some tickets in Metrics/Cloud #33309->33313;#32725

Write some simple scripts to generate ID hexes of relays with certain properties as input for #33260.

Tickets that needs reviewers: #29365, #33076, #33257

Anything that people want to bring? Anybody block on anything?