[Author Prev][Author Next][Thread Prev][Thread Next][Author Index][Thread Index]
Re: [tor-bugs] #19021 [Metrics/CollecTor]: improve configuration process
#19021: improve configuration process
-------------------------------+------------------------
Reporter: iwakeh | Owner: iwakeh
Type: enhancement | Status: new
Priority: High | Milestone:
Component: Metrics/CollecTor | Version:
Severity: Normal | Resolution:
Keywords: ctip operation | Actual Points:
Parent ID: | Points:
Reviewer: | Sponsor:
-------------------------------+------------------------
Comment (by karsten):
Replying to [comment:3 iwakeh]:
> Does the following topic from the RoadMap mean that Torperf data
fetching will be obsolete in CollecTor then?
> {{{Take Torperf offline; karsten; 2016-09-30 }}}
Possibly, yes. The plan is to switch from Torperf to OnionPerf, and
OnionPerf might come with its own code to fetch data from other OnionPerf
instances and make that available to the world. But I'm not entirely
certain which role CollecTor will play once OnionPerf is in place. We
might be able to remove the code that merges .data and .extradata files,
but we might need to keep the Torperf results archiving code. I'd say
don't give up on the Torperf module in CollecTor just yet.
--
Ticket URL: <https://trac.torproject.org/projects/tor/ticket/19021#comment:4>
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