#29370: Measure mode with arbitrary tgen traffic models
---------------------------------------+------------------------------
Reporter: irl | Owner: metrics-team
Type: enhancement | Status: reopened
Priority: Low | Milestone:
Component: Metrics/Onionperf | Version:
Severity: Normal | Resolution:
Keywords: metrics-team-roadmap-2020 | Actual Points:
Parent ID: #33321 | Points: 1
Reviewer: | Sponsor: Sponsor59
---------------------------------------+------------------------------
Changes (by karsten):
* cc: robgjansen, jnewsome (added)
Comment:
What is the use case here? Is this about providing TGen traffic models
that are otherwise used in Shadow, but for more complex user models than
bulk file downloads? OnionPerf users are not expected to generate these
model files on their own, neither from scratch nor by editing existing
model files, right?
One technical problem I see is that TGen models generated by OnionPerf
contain measurement details like peers (server addresses) or ports (SOCKS
port of the local Tor client). Would the provided models contain
placeholders for these parts that OnionPerf fills in before passing models
to its TGen instances? How does Shadow solve this problem?
Related to this ticket, we might want to implement #33243 by providing a
traffic model file rather than by adding more command line parameters. In
fact, we could take out the `--oneshot` parameter if we provide a traffic
model file for it.
Implementation note: OnionPerf already contains a `-m/--traffic-model`
parameter that does not do anything right now and that we would implement
here.
--
Ticket URL: <https://trac.torproject.org/projects/tor/ticket/29370#comment:6>
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
