-----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