[tor-bugs] #5336 [Analysis]: Do simulations of initial proposal 182 patch

[Tor Bug Tracker & Wiki]

#5336: Do simulations of initial proposal 182 patch
----------------------+-----------------------------------------------------
 Reporter:  arma      |          Owner:              
     Type:  task      |         Status:  needs_review
 Priority:  normal    |      Milestone:              
Component:  Analysis  |        Version:              
 Keywords:            |         Parent:  #4682       
   Points:            |   Actualpoints:              
----------------------+-----------------------------------------------------

Comment(by robgjansen):

 Replying to [comment:19 karsten]:
 > Replying to [comment:18 robgjansen]:
 > > 1. Print the heartbeat message every second instead of every minute
 with $ scallion --heartbeat-frequency=1 …
 > > 2. The heartbeat message will contain the number of bytes each nodes
 sends and receives per second. Match that up with the relay bandwidth
 limits to determine if nodes are actually obeying their bandwidth limits.
 You probably have to either modify the parse() function in analyze.py, or
 write a new script for this.
 >
 > Done.  I wrote my own script and made two graphs: the
 [https://trac.torproject.org/projects/tor/attachment/ticket/5336/task5336-bwrate-2012-10-03.png
 first graph] compares bandwidth rates to median bandwidths, and the
 [https://trac.torproject.org/projects/tor/attachment/ticket/5336/task5336-bwburst-2012-10-03.png
 second graph] compares bandwidth bursts to 99th percentiles.  For me it
 looks like all three branches respect bandwidth rates quite well and do
 '''not''' respect bandwidth bursts as much as they should.  I do not see
 major differences between the three branches.  I wonder if there's a
 better way to visualize this.

 It may make sense that the amount sent on the wire is slightly more than
 the bandwidth 99th percentile bandwidth sent in Tor ( b/c control packets,
 packet header overheads, etc, are included in the amount sent on the wire
 but not in Tor's limits).

 >
 > > The per-node memory tracking is not working yet in Shadow, so we'll
 only be able to say things about overall memory consumption by looking at
 the data/dstat.log file.
 >
 > I have the three dstat.log files.  What do I do with them?

 I believe the first few lines contain header info that explains the format
 of the csv. One of the columns has a timestamp and another has the system
 memory usage. You should be able to draw a memory-over-time plots with
 those two columns, and compare each branch in the same graph. (note that
 this is total system memory usage, so this would only work if nothing else
 is consuming memory on these machines - which should be the case if you
 used EC2)

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