<!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Transitional//EN"
"http://www.w3.org/TR/xhtml1/DTD/xhtml1-transitional.dtd">
<html xmlns="http://www.w3.org/1999/xhtml">
<head>
<meta http-equiv="Content-Type" content="text/html; charset=utf-8" />
<title></title>
</head>
<body>
<div>Hi,
<br />
are you useing cat7 cable?
<br />
Did you configure a DNS fall-back 8.8.8.8 to be on the safe side?
<br />
<br />
Ok, with (1000 mBit x2=) 2000mBit you are handling 114,3 MB/s
<br />
<br />
16,8
<br />
+2,7
<br />
+9,6
<br />
+19,7
<br />
+26,2
<br />
+7,0
<br />
+22,6
<br />
+9,7
<br />
= 114,3 MB/s
<br />
<br />
Thats already good. Did you declare a cut-off?
<br />
You can experimentally try my follwing advice:
<br />
For each Tor process set in torrc:
<br />
BandwidthRate 13000000 bytes
<br />
BandwidthBurst 13375000 bytes
<br />
<br />
So you end up with
<br />
Server1: 4x 13000000 bytes = 4x13MB/s
<br />
Server2: 4x 13000000 bytes = 4x13MB/s
<br />
(in each direction)
<br />
104+104=208 MB/s
<br />
You hopefully will end up with ~540TB per month.
<br />
<br />
(oh, don't miss your upgrade to 0.2.7.6)
<br />
(-:
<br />
<br />
<br />
<div>
<div>Am Sonntag, 13. Dezember 2015 21:18 schrieb Dirk Eschbach <tor-relay.dirk@o.banes.ch>:
<br />
</div>
<blockquote type="cite">
<div>Hello all,
<br />
<br />
we are administrating 2 Tor Exits for privacyfoundation.ch [1].
<br />
<br />
In the last month we realized that the traffic which is going through
<br />
our servers / throughput is
<br />
by far less than the machines and the providers network can handle.
<br />
We were internally and recently with Moritz from torservers.net looking
<br />
at this problem but could
<br />
not find a way to improve throughput.
<br />
Even on the same machine the throughput between servers varies a lot
<br />
with out any visible reason.
<br />
<br />
I hope you can help.
<br />
<br />
Our setup is two servers with a maximum of 4 tor processes (exit) each.
<br />
Looking at CPU, Disk, RAM and so on the machines are not busy at all.
<br />
<br />
Konsole output
<br />
top - 09:57:49 up 16 days, 11:57, 1 user, load average: 1.14, 0.91, 0.81
<br />
Tasks:244 total, 3 running,241 sleeping, 0 stopped, 0 zombie
<br />
%Cpu0 :12.5 us, 3.4 sy, 0.0 ni,79.7 id, 0.0 wa, 0.0 hi, 4.4 si, 0.0 st
<br />
%Cpu1 :15.9 us, 5.4 sy, 0.0 ni,74.3 id, 0.3 wa, 0.0 hi, 4.1 si, 0.0 st
<br />
%Cpu2 :14.3 us, 2.7 sy, 0.0 ni,77.0 id, 0.0 wa, 0.0 hi, 6.0 si, 0.0 st
<br />
%Cpu3 : 9.5 us, 3.4 sy, 0.0 ni,80.3 id, 0.0 wa, 0.0 hi, 6.8 si, 0.0 st
<br />
KiB Mem: 3877624 total, 2739880 used, 1137744 free, 1288 buffers
<br />
KiB Swap: 4026364 total, 364264 used, 3662100 free. 10752 cached Mem
<br />
<br />
Looking at the network connection it is without any problem possible to
<br />
start big downloads without reducing TOR throughput.
<br />
The servers are connected with 1 Gbit/s each.
<br />
<br />
The big question now is:
<br />
Why do the machines do not have more throughput ?
<br />
Is the reason for this the way the distribution through the Tor network
<br />
works.
<br />
Moritz hinted it might have to do with the way the tor "bandwidth
<br />
scanners" measure the ability of a server to handle traffic.
<br />
<br />
Can you explain me / point me to documentation where this process is
<br />
described and how this can be optimized.
<br />
What are the criteria for tor exit node server traffic distribution ?
<br />
How do the clients choose the exit ?
<br />
<br />
I would be very happy if you could provide some answers / documentation
<br />
which will set me on the right track.
<br />
<br />
Thanks very much for you help.
<br />
<br />
Dirk
<br />
<br />
[1] https://globe.torproject.org/#/search/query=digiges
<br />
<br />
<br />
_______________________________________________
<br />
tor-relays mailing list
<br />
tor-relays@lists.torproject.org
<br />
https://lists.torproject.org/cgi-bin/mailman/listinfo/tor-relays</div>
</blockquote>
</div>
</div>
</body>
</html>