On Fri, Jun 13, 2014 at 12:54 AM, Mirimir <miri...@riseup.net> wrote: > http://bayimg.com/lAoiMAAfL > >> For three of the ten exits used (default client choices) in the first >> test series, http://craigslist.org/ loaded in about eight seconds (30-50 >> Kbps). For the other seven, it took several minutes (~1 Kbps). >> >> I don't see any obvious correlation with blacklist status.
Since you seem to be letting tor pick its exits, sampling for days might give a wider representative spread of exits. And could plot things for each exit over time. I see major prevalence of variation in your returned page lengths in bytes, almost every exit varied. Only about 1% of my single fetch across 1200+ exits varied from the exact normal byte count. It should be determined whether tor software somehow causes this when carrying 'slow' packet streams. By running in a loop the fetch from bound to the exit IP of an exit relay affected by both slowblocking, and showing byte variance. No more variance = tor issue. Still variance = IP <--> CL stack/path issue, or CL issue alone. Will look at your Midori tool and maybe more of this type of project sometime later. -- tor-talk mailing list - tor-talk@lists.torproject.org To unsubscribe or change other settings go to https://lists.torproject.org/cgi-bin/mailman/listinfo/tor-talk
