[Author Prev][Author Next][Thread Prev][Thread Next][Author Index][Thread Index]
[tor-bugs] #1919 [Metrics]: Set up a few new torperfs with fixed sets of entry guards
#1919: Set up a few new torperfs with fixed sets of entry guards
---------------------+------------------------------------------------------
Reporter: arma | Owner: karsten
Type: defect | Status: new
Priority: normal | Milestone: Deliverable-Sep2010
Component: Metrics | Version:
Keywords: | Parent: #1766
---------------------+------------------------------------------------------
In theory, the results of #1918 (annotate torperf fetches by path) should
let us simulate the expected performance of Tor users that use various
combinations of guard nodes: just grab all the requests that use the
guards you're simulating using, and make a torperf graph out of just those
requests.
The problem is that the CBT feature will alter Tor's circuit build timeout
based on the average build times of all nodes, not just the guards we're
pretending we used, so we won't be able to capture the whole picture.
How different will the results be? To get some intuition, we should run
several torperf install with cbt enabled and various sets of guards. Then
when we have enough annotated torperf runs, we'll be able to compare the
simulated results with the actual results, and make some decisions about
what went wrong.
So the first question is: what combinations of guards should we try using?
Mike, do you have any good guesses here?
--
Ticket URL: <https://trac.torproject.org/projects/tor/ticket/1919>
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