#7358: Decide on list of stats to collect
------------------------------------------------------------------------+---
Reporter: robgjansen |
Owner:
Type: task |
Status: new
Priority: normal |
Milestone: Tor: unspecified
Component: Tor |
Version:
Keywords: performance, simulation, statistics, tor-relay, tor-client |
Parent: #7357
Points: |
Actualpoints:
------------------------------------------------------------------------+---
Comment(by karsten):
Replying to [comment:4 robgjansen]:
> I'm of the opinion that we let the user application (TorPerf, etc.)
continue measuring end-user-specific performance characteristics,
precisely because of the lack of information and imprecision that you
mentioned. Tor should stick to things its good at measuring, like
throughput.
Ah, okay. I read your statement in #7357 ("Not only will this standardize
stats across simulations/real experiments/tor metrics, clients like
TorPerf would only have to worry about creating requests and not
collecting stats."), and I found the idea of having Tor output basic
performance data about Torperf's download tempting. But either way works.
--
Ticket URL: <https://trac.torproject.org/projects/tor/ticket/7358#comment:7>
Tor Bug Tracker & Wiki <https://trac.torproject.org/>
The Tor Project: anonymity online
_______________________________________________
tor-bugs mailing list
[email protected]
https://lists.torproject.org/cgi-bin/mailman/listinfo/tor-bugs
