[tor-bugs] #7241 [Analysis]: Visualize how quickly the Tor network changes

Tor Bug Tracker & Wiki blackhole at torproject.org
Fri Jan 4 13:19:07 UTC 2013


#7241: Visualize how quickly the Tor network changes
----------------------+-----------------------------------------------------
 Reporter:  asn       |          Owner:              
     Type:  task      |         Status:  needs_review
 Priority:  normal    |      Milestone:              
Component:  Analysis  |        Version:              
 Keywords:            |         Parent:  #2681       
   Points:            |   Actualpoints:              
----------------------+-----------------------------------------------------
Changes (by peer):

  * status:  new => needs_review


Comment:

 The data and graphs are from a first pass analysis. s2012.csv should be a
 complete view of 2012 and was generated using data from 2012 and December
 2011.

 == Definitions ==

 Let Y be the consensus listed (now) and X the consensus some hours ago
 (now - hours).

 frac_relay is the number of routers in Y that are also in X based on
 fingerprint, divided by the total number of routers in Y.

 frac_cw is ratio of bandwidth sum from X arising from routers in both X
 and Y divided by the bandwidth sum from Y of routers in both X and Y.

 == Notes ==

 Some hourly consensus documents were missing and comparisons involving
 those documents were ignored (no special handling).

 A router that is present in both Y and X could be missing from a consensus
 document between [now, now-hours], but this situation is currently ignored
 due to processing time.

 Some ratios in the frac_cw graphs are odd. A quick look at the data shows:

 {{{
 (sum of cw for routers in both X and Y for X, sum of cw for routers in
 both X and Y for Y)
 consensus,hours,frac_relays,frac_cw,month,day,day_of_week
 (9819752, 7841626)
 2012-04-17-13-00-00-consensus,1,0.969956,1.252260,4,17,2
 (9764530, 2363373)
 2012-04-17-13-00-00-consensus,2,0.955540,4.131608,4,17,2
 (9398785, 2323009)
 2012-04-17-13-00-00-consensus,3,0.952431,4.045953,4,17,2
 (9206152, 8152643)
 2012-04-17-13-00-00-consensus,4,0.946181,1.129223,4,17,2
 (9519503, 9373338)
 2012-04-17-13-00-00-consensus,5,0.933105,1.015594,4,17,2
 (9727357, 9408589)
 2012-04-17-13-00-00-consensus,6,0.934238,1.033881,4,17,2
 (9375476, 7251736)
 2012-04-17-13-00-00-consensus,12,0.897784,1.292860,4,17,2
 (9758498, 7935133)
 2012-04-17-13-00-00-consensus,24,0.896715,1.229784,4,17,2
 (9674191, 6843889)
 2012-04-17-13-00-00-consensus,36,0.872363,1.413552,4,17,2
 (9141303, 8071610)
 2012-04-17-13-00-00-consensus,48,0.848475,1.132525,4,17,2
 (9591979, 8984097)
 2012-04-17-13-00-00-consensus,72,0.839209,1.067662,4,17,2
 (9586237, 8260454)
 2012-04-17-13-00-00-consensus,96,0.849177,1.160498,4,17,2
 (9061210, 6923951)
 2012-04-17-13-00-00-consensus,120,0.836865,1.308676,4,17,2
 (9306138, 8460224)
 2012-04-17-13-00-00-consensus,144,0.821573,1.099987,4,17,2
 (9184215, 8564116)
 2012-04-17-13-00-00-consensus,168,0.812981,1.072407,4,17,2
 }}}

 == Questions ==

 What can be done to parse and operate on the consensus data more quickly?
 s2012.csv took around 12 hours to generate with pypy first_pass.py and
 limited memory.

 Any insight into the missing hourly consensus documents?

 Anyone want to try working with the first pass data?

-- 
Ticket URL: <https://trac.torproject.org/projects/tor/ticket/7241#comment:2>
Tor Bug Tracker & Wiki <https://trac.torproject.org/>
The Tor Project: anonymity online


More information about the tor-bugs mailing list