[Author Prev][Author Next][Thread Prev][Thread Next][Author Index][Thread Index]
Re: [tor-bugs] #21759 [Metrics/CollecTor]: Add persistence for torperf/onionperf
#21759: Add persistence for torperf/onionperf
-------------------------------+---------------------------------
Reporter: iwakeh | Owner: iwakeh
Type: enhancement | Status: needs_review
Priority: Medium | Milestone: CollecTor 1.3.0
Component: Metrics/CollecTor | Version:
Severity: Normal | Resolution:
Keywords: | Actual Points:
Parent ID: | Points:
Reviewer: | Sponsor:
-------------------------------+---------------------------------
Changes (by iwakeh):
* status: needs_information => needs_review
Comment:
Assuming 'no' for the question in comment:3 (store only one file in out)
and 'yes' for comment:4 please find
[https://gitweb.torproject.org/user/iwakeh/collector.git/commit/?h=task-21759&id=28c402e370ed45185caf39737a8be431b8d966d2
this branch] for review.
This branch introduces sync-functionality for Onionperf, but not yet
storing via the persistence mechanism, because the latter is currently
implemented using an implicit transaction, i.e., all descriptors in one
downloaded descriptor file are only stored, if all were valid. This is
different from the sync-approach where invalid/unparseable descriptors are
ignored, but valid ones stored no matter if they came in one file.
Could the sync-approach be also used for directly downloaded descriptors?
--
Ticket URL: <https://trac.torproject.org/projects/tor/ticket/21759#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