> On 16 Sep 2016, at 07:58, Ralph Seichter <tor-relays-ml@xxxxxxxxxxx> wrote: > > I have made some measurements. Downloading large files through Tor did > not appear to show significant differences between both nodes, which > could mean that Tor clients are either capped in general or the circuits > were overall not fast enough to make my nodes reach their limits. > > I also tried several iperf3 bandwidth measurements between the two Tor > nodes and a third server which I know to be reliably fast. My Tor node > #1 averaged 697 Mbits/sec, and #2 averaged 505 Mbits/sec -- while Tor > was running on both nodes. I tried this with both IPv4 and IPv6, the > latter being slightly faster. > > It would appear that even though #2 has less bandwidth than #1, the > available bandwidth of #2 is more than 10 times the bandwidth utilized > by Tor on this machine. I still don't understand why TorRelay02HORUS is > just limping along. A few things that affect consensus weight happen at random: * client usage, which affects observed bandwidth, which limits consensus weight, * the timing and pairing of bandwidth authority measurement, which limits consensus weight, It's possible that by chance, 02 got a bad measurement a week ago, and 01 got a good one. Give it a few more weeks, and see if the measurements even out. Tim > > -Ralph > _______________________________________________ > tor-relays mailing list > tor-relays@xxxxxxxxxxxxxxxxxxxx > https://lists.torproject.org/cgi-bin/mailman/listinfo/tor-relays Tim Wilson-Brown (teor) teor2345 at gmail dot com PGP C855 6CED 5D90 A0C5 29F6 4D43 450C BA7F 968F 094B ricochet:ekmygaiu4rzgsk6n xmpp: teor at torproject dot org
Attachment:
signature.asc
Description: Message signed with OpenPGP using GPGMail
_______________________________________________ tor-relays mailing list tor-relays@xxxxxxxxxxxxxxxxxxxx https://lists.torproject.org/cgi-bin/mailman/listinfo/tor-relays