#33076: Graph onionperf and consensus information from Rob's experiments -----------------------------------------+-------------------------------- Reporter: mikeperry | Owner: metrics-team Type: task | Status: needs_revision Priority: Medium | Milestone: Component: Metrics/Analysis | Version: Severity: Normal | Resolution: Keywords: metrics-team-roadmap-2020Q1 | Actual Points: Parent ID: | Points: Reviewer: | Sponsor: -----------------------------------------+--------------------------------
Comment (by mikeperry): Replying to [comment:8 karsten]: > There's one line per consensus entry, which is where we get the following columns from: `fingerprint,validafter,hasexitflag,hasguardflag,measured`. The `read` and `write` columns come from bandwidth histories contained in extra-info descriptors. `rate,burst,observed` come from the server descriptor referenced by the consensus entry. > > For CDF-Relay-Utilization I used (pseudo code): > > {{{ > read_write := (read + written) / 2; > advertised := min(rate, burst, observed) > plot -> advertised / read_write > }}} Let's do: {{{ read_write := (read + written) / 2; peak := max(rate, burst, observed) plot -> read_write / peak }}} Ideally, peak would be that peak-in-30-days thing we grinded out in Whistler, but for this we actually wanna see what the instantaneous change to peak that the experiment caused did to results. The of plot should still be between 0 and 1.0. Any relay that has a value over 1.0 would be very interesting to look at. > For CDF-Relay-Stream-Capacity I used: > > {{{ > plot -> measured / observed > }}} Yes, I think this is just off by a factor of 1000 then. It should be: {{{ plot -> 1000*measured / observed }}} And then the CDFs will be centered on 1.0. -- Ticket URL: <https://trac.torproject.org/projects/tor/ticket/33076#comment:9> Tor Bug Tracker & Wiki <https://trac.torproject.org/> The Tor Project: anonymity online
_______________________________________________ tor-bugs mailing list tor-bugs@lists.torproject.org https://lists.torproject.org/cgi-bin/mailman/listinfo/tor-bugs