-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1
I have multiple relays running on the following systems: - - vmware vsphere virtualization technology - - 100 mbps port - - 1GB dedicated RAM - - 2.6 Ghz 1 core CPU dedicated - - OS: FreeBSD 10.0 Release amd64 or Debian Stable - - DO NOT KNOW IF I HAVE AES-NI SUPPORT OR HOW TO ACTIVATE IT (?)
Currently atlas shows 3-4-5 MB/s advertised bandwidth for these relays. Arm shows between 600 and 1200 concurrent circuits (total of inbound, outbound and exit) and average traffic consumption is 5-6 TB per month (total both download and upload). I think this can be improved, but how? The servers have only purpose Tor, there is nothing else running on them and there is no bandwidth cap or throttling.
Suggestions? Thanks in advance.
- -- s7r PGP Fingerprint: 7C36 9232 5ABD FB0B 3021 03F1 837F A52C 8126 5B11
-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1
On 07/01/2014 08:46 PM, s7r wrote:
I have multiple relays running on the following systems: - vmware vsphere virtualization technology - 100 mbps port - 1GB dedicated RAM - 2.6 Ghz 1 core CPU dedicated - OS: FreeBSD 10.0 Release amd64 or Debian Stable
- DO NOT KNOW IF I HAVE AES-NI SUPPORT OR HOW TO ACTIVATE IT (?)
$ cat /proc/cpuinfo | grep aes
If it returns a string of instruction sets, your CPU has the AES-NI instruction set. If it returns nothing, it doesn't.
Currently atlas shows 3-4-5 MB/s advertised bandwidth for these relays. Arm shows between 600 and 1200 concurrent circuits (total of inbound, outbound and exit) and average traffic consumption is 5-6 TB per month (total both download and upload). I think this can be improved, but how?
What does the CPU usage of the tor process look like? How long have your relays been running? It takes a while until a relay reaches a steady state. [1] Can you tell us the fingerprints of your relays?
At least in terms of your hardware, you should be able to roughly saturate your 100 Mbit/s line.
[1] https://blog.torproject.org/blog/lifecycle-of-a-new-relay
-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1
On 7/1/2014 10:07 PM, Random Tor Node Operator wrote:
On 07/01/2014 08:46 PM, s7r wrote:
I have multiple relays running on the following systems: - vmware vsphere virtualization technology - 100 mbps port - 1GB dedicated RAM - 2.6 Ghz 1 core CPU dedicated - OS: FreeBSD 10.0 Release amd64 or Debian Stable
- DO NOT KNOW IF I HAVE AES-NI SUPPORT OR HOW TO ACTIVATE IT (?)
$ cat /proc/cpuinfo | grep aes
It does not return anything. I have the proc folder, but there is no cpuinfo file in it. Here:
root@tor:/ # cat /proc/cpuinfo | grep aes cat: /proc/cpuinfo: No such file or directory
If it returns a string of instruction sets, your CPU has the AES-NI instruction set. If it returns nothing, it doesn't.
Currently atlas shows 3-4-5 MB/s advertised bandwidth for these relays. Arm shows between 600 and 1200 concurrent circuits (total of inbound, outbound and exit) and average traffic consumption is 5-6 TB per month (total both download and upload). I think this can be improved, but how?
What does the CPU usage of the tor process look like?
PID USERNAME THR PRI NICE SIZE RES STATE TIME WCPU COMMAND 675 _tor 2 20 0 130M 126M sbwait 567:31 7.96% tor Uses maximum 10-12% of the available CPU. Uses maximum 150 - 160 MB of RAM. (~15%)
How long have your relays been running? It takes a while until a relay reaches a steady state. [1]
Little over 2 months if I recall correct. Exit, Guard, Stable and Fast.
Can you tell us the fingerprints of your relays?
here is one I am freebie hired to maintain: 6C36F9ACBA57AC9C10DBC39D330CFA337522E72B
At least in terms of your hardware, you should be able to roughly saturate your 100 Mbit/s line.
[1] https://blog.torproject.org/blog/lifecycle-of-a-new-relay _______________________________________________ tor-relays mailing list tor-relays@lists.torproject.org https://lists.torproject.org/cgi-bin/mailman/listinfo/tor-relays
Thank you for prompt reply and looking forward for your help.
- -- s7r PGP Fingerprint: 7C36 9232 5ABD FB0B 3021 03F1 837F A52C 8126 5B11
-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1
root@tor:/ # cat /proc/cpuinfo | grep aes cat: /proc/cpuinfo: No such file or directory
According to a stackoverflow page [2], you can look for hints indicating the existence of AES-NI support in "sysctl hw" and /var/run/dmesg.boot
PID USERNAME THR PRI NICE SIZE RES STATE TIME WCPU COMMAND 675 _tor 2 20 0 130M 126M sbwait 567:31 7.96% tor Uses maximum 10-12% of the available CPU. Uses maximum 150 - 160 MB of RAM. (~15%)
okay, so CPU doesn't seem to be a bottleneck, as expected.
You could try downloading a large (some 100 MBs) file from a fast server via wget to see whether you can saturate your downstream.
here is one I am freebie hired to maintain: 6C36F9ACBA57AC9C10DBC39D330CFA337522E72B
It is an Exit relay. I am not sure, maybe Tor is designed in a way that Exits are strongly preferred for Exit connections, so they get less traffic for HSDir/V2Dir requests or for being a Rendezvous Point or Introduction Point for Hidden Services. That is mostly speculation on my part though. I never had any Exit relays on my own. Probably the Tor Path Specification [3] has the answer to that question.
Your relay seems to be the only one in that /16 subnet, so that wouldn't be a reason for less-than-normal traffic.
[2] http://stackoverflow.com/questions/4083848/what-is-the-equivalent-of-proc-cp...
[3] https://gitweb.torproject.org/torspec.git?a=blob_plain;hb=HEAD;f=path-spec.t...
On Tue, Jul 1, 2014 at 3:24 PM, s7r s7r@sky-ip.org wrote:
dedicated RAM - 2.6 Ghz 1 core CPU dedicated - OS: FreeBSD 10.0 Release amd64
- DO NOT KNOW IF I HAVE AES-NI SUPPORT OR HOW TO ACTIVATE IT (?)
It does not return anything. I have the proc folder, but there is no cpuinfo file in it. Here:
root@tor:/ # cat /proc/cpuinfo | grep aes cat: /proc/cpuinfo: No such file or directory
That's because FreeBSD is not Linux, its proc is limited to procfs(5) with non process info/knobs in sysctl(8), nor is it really necessary to mount proc. Also, 'aes' is presented in CAPS. That single core might be old enough to not have it. Check: /var/run/dmesg.boot http://svnweb.freebsd.org/ports/head/misc/cpuid/ [also available via ftp package] openssl speed aes
tor-relays@lists.torproject.org
-
grarpamp -
Random Tor Node Operator -
s7r