-----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 SIGNATURE----- Version: GnuPG v2.0.22 (MingW32) iQEcBAEBAgAGBQJTswsDAAoJEIN/pSyBJlsRws0IAItoJ1gQxlfKwmBIuUHgsAyJ FA2F1s/N4tU4zrC8oLQEayI8nKNRyRK8armLRRm1fDOR5ZomRov/ThnJA55boZv/ RF8p4aMNSAehOJAGgRbUwFmjL4NTuvZBEeC8TOHrDSKX6SB2R210RhyucBpRID3C l2D7nITPnqGVM3zeZ3d79LMWGo9MQ6CBYHosE4MmmVCwYPI3abRDXNLWEdii7AvR 1qt24HQeartxf1AIiJRph05/PlZRbh0RkdATz+lYeAhwz0ryRkncYbU8SRkK5jnf s5VwqDqOuUDp1k7Grn7f7SERwCzlNKWhg1kLfxKWevBL4Q8WX47Xvjaw827dPUg= =mYES -----END PGP SIGNATURE-----