[tor-relays] optimize performance of a relay running on a VM

Random Tor Node Operator tor at unterderbruecke.de
Tue Jul 1 20:12:29 UTC 2014


-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1

> root at 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-cpuinfo-on-freebsd-v8-1

[3]
https://gitweb.torproject.org/torspec.git?a=blob_plain;hb=HEAD;f=path-spec.txt
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.11 (GNU/Linux)
Comment: Using GnuPG with Thunderbird - http://www.enigmail.net/

iQIcBAEBAgAGBQJTsxYkAAoJEJe61A/xrcOQ1WUQAKzb4xSA8Wz0u3T4sCn2Q41g
URTA4Q9OGDxRvYpO2I9cXOuu4pj2g+jWsxOH1uX8g1O6uY7u6n5cYj0FYczbDSJm
wn9ySxIo8wJAZCTStJmXQhgm9oceq7EDgiVsRQAXQilkv3i2JnfToNLMH80vMuKH
x6Wj6lfzEWs2/8NG/WxNmJuv4O7w/mPJ1LeCqLsuL8O3ni03Ql0iPnohyhbQrJCo
vAbKaj1ix65eSNahLqcH53MF3x+FkkG0ULTgWebjCg731kqVFOzsrRQQY4oZXo+k
+fx+7kodjqQdQ7xSRpaTBe/15NE8Xk8hT9Ib9jVQ9Zyo19EcP6NIxnYC+zJD2G++
xQtcpur6N5XZCruuC+GoUsdYB/6lrLJHJ+SaqXachhEfqcXm1DaIH0wJb7Zre2Jf
4eS/H/Fp0+msKFHq3ElL7TcnxpMOMUkoAp4d7jbi8v/0u5DHuMRQDVTlIfpSX3fJ
HMBQo9K1jf1iInCx7vpLFe7f+m5tH+PRTME8ZBTJ6PnAUbrrQW4khBF8P3J6gqm9
1DTH16BF+B2zNhQhyKI9c8T6CFIxXdnTwUAYFwHA8GQII6qP2M2ykK9ELpN1y/o8
dFTOMe017L4jM+73yhoNIddbGoCqBlIGu+1vv/OK/uk+s5Lmh3fveajOsECAcBpq
HzlYGmmOy6UuWsClZL+X
=fnHk
-----END PGP SIGNATURE-----


More information about the tor-relays mailing list