[Author Prev][Author Next][Thread Prev][Thread Next][Author Index][Thread Index]

Re: [tor-bugs] #25774 [Metrics/Ideas]: Record latency measurements using OnionPerf



#25774: Record latency measurements using OnionPerf
---------------------------+--------------------------------
 Reporter:  irl            |          Owner:  metrics-team
     Type:  project        |         Status:  needs_revision
 Priority:  Medium         |      Milestone:
Component:  Metrics/Ideas  |        Version:
 Severity:  Normal         |     Resolution:
 Keywords:                 |  Actual Points:
Parent ID:                 |         Points:
 Reviewer:  irl            |        Sponsor:
---------------------------+--------------------------------

Comment (by karsten):

 Replying to [comment:4 karsten]:
 > Replying to [comment:3 irl]:
 > > End-to-end latency is the latency to send data across the circuit.
 From looking at the TorPerf spec, this would be the difference between
 DATAREQUEST and DATARESPONSE divided by 2.
 >
 > Aha! I'll make another graph for that. Do we want to do the division-
 by-2 step here, which includes the implicit assumption that both
 directions are equally fast, or do we want to use a round-trip metric of
 some kind? Just thinking about what would be more intuitive, that is,
 least confusing for users.

 I made a plot with round-trip latencies by onion vs. public server:

 [[Image(latencies.png, 700px)]]

 What do you think?

 And was there another graph we discussed in Aberdeen that we could make
 from existing data? I vaguely recall we discussed three possible graphs,
 but I don't remember whether all three of them would use existing data.

--
Ticket URL: <https://trac.torproject.org/projects/tor/ticket/25774#comment:5>
Tor Bug Tracker & Wiki <https://trac.torproject.org/>
The Tor Project: anonymity online
_______________________________________________
tor-bugs mailing list
tor-bugs@xxxxxxxxxxxxxxxxxxxx
https://lists.torproject.org/cgi-bin/mailman/listinfo/tor-bugs