Hello all ! o/ It seems I am running into a performance issue with my relay, and I am not able to troubleshoot it, so I hope someone could point out something obvious I am missing! (for information, the relay is a 2vCPU, 2G RAM VM running on Scaleway) From what I observe from the graphs, my maximal CPU usage ceils at ~60%, and the load ceils at 1 eventhough the TOR daemon is aware I have 2 cores available, and I set the NumCPUs configuration option accordingly) First I tought that the network did not want to send me more traffic, but my graphs are way too regular to make this eventuality plausible, so I am pretty convinced that it is due to a lack of optimization on my side. (link to my graphs for reference http://www.noelshack.com/2017-01-1483803911-constancesurvingt.png this is a 1 hour snapshot, but it has been this constant for at least one day) My first hypothesis was that the daemon is running out of file descriptors, so I raised the limit that was in the defaults (doubled it actually, by editing /etc/init.d/tor like a pig, to test), but I did not observe any change in Grafana. It is supposed to be caped at 20MBps, and 25MBps burst so I doubt the limitation I am observing is enforced by the node itself. If anyone had any pointers I would be grateful! Cheers! -- Thomas
On Sat, 7 Jan 2017 16:55:12 +0100 Thomas Maurice <thomas@maurice.fr> wrote:
It is supposed to be caped at 20MBps, and 25MBps burst so I doubt the limitation I am observing is enforced by the node itself.
You mean traffic limitation in torrc? Remove it. There is no reason to apply bandwidth caps unless you want to run other tasks on the same connection, or it's metered per transfer amounts. If neither is the case, you only tie down your Tor with pointless housekeeping to track limits (which likely won't be reached anyways). As for what to do for better utilization, set up a second instance of Tor. Tor is poorly multithreaded, and one instance on its own, even with NumCPU specified, is not able to utilize more than about 1.3 CPU cores. -- With respect, Roman
Hello Thomas. You may also have a look at this article if it helps and in case this is a new Tor Relay node: https://blog.torproject.org/blog/lifecycle-of-a-new-relay Cheers, Dr Ciphers ---- On Sat, 07 Jan 2017 17:55:12 +0200 Thomas Maurice <thomas@maurice.fr> wrote ---- Hello all ! o/ It seems I am running into a performance issue with my relay, and I am not able to troubleshoot it, so I hope someone could point out something obvious I am missing! (for information, the relay is a 2vCPU, 2G RAM VM running on Scaleway)
From what I observe from the graphs, my maximal CPU usage ceils at ~60%,
and the load ceils at 1 eventhough the TOR daemon is aware I have 2 cores available, and I set the NumCPUs configuration option accordingly) First I tought that the network did not want to send me more traffic, but my graphs are way too regular to make this eventuality plausible, so I am pretty convinced that it is due to a lack of optimization on my side. (link to my graphs for reference http://www.noelshack.com/2017-01-1483803911-constancesurvingt.png this is a 1 hour snapshot, but it has been this constant for at least one day) My first hypothesis was that the daemon is running out of file descriptors, so I raised the limit that was in the defaults (doubled it actually, by editing /etc/init.d/tor like a pig, to test), but I did not observe any change in Grafana. It is supposed to be caped at 20MBps, and 25MBps burst so I doubt the limitation I am observing is enforced by the node itself. If anyone had any pointers I would be grateful! Cheers! -- Thomas _______________________________________________ tor-relays mailing list tor-relays@lists.torproject.org https://lists.torproject.org/cgi-bin/mailman/listinfo/tor-relays
-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA256 On 01/07/2017 08:00 PM, Efthimis Iosifdis wrote:
You may also have a look at this article if it helps and in case this is a new Tor Relay node:
/me wonders if this link should be added to the IRC channel topic list too. - -- Toralf PGP: C4EACDDE 0076E94E -----BEGIN PGP SIGNATURE----- iHYEAREIAB4FAlhxQcMXHHRvcmFsZi5mb2Vyc3RlckBnbXguZGUACgkQxOrN3gB2 6U6tZwD7BjyflP5pswzFy+DBH0i3/ISClQ5/1plrrNNPI7C7CxkA+gIvRwh5cQRS nhqBBU/8wyKX+bJRN15xjeAZl6RAcNgG =meFV -----END PGP SIGNATURE-----
Hello of course I read the documentation before asking, I do not want to make useless noise on this channel. I'll try Roman's solution! On 01/07/2017 08:30 PM, Toralf Förster wrote:
On 01/07/2017 08:00 PM, Efthimis Iosifdis wrote:
You may also have a look at this article if it helps and in case this is a new Tor Relay node:
/me wonders if this link should be added to the IRC channel topic list too.
_______________________________________________ tor-relays mailing list tor-relays@lists.torproject.org https://lists.torproject.org/cgi-bin/mailman/listinfo/tor-relays
-- EESTEC International - IT Team Head Administrator https://eestec.net Web: https://thomas.maurice.fr - thomas@maurice.fr Skype: thom.maurice LinkedIn: https://www.linkedin.com/in/thomas-maurice-80846b61
participants (4)
-
Efthimis Iosifdis -
Roman Mamedov -
Thomas Maurice -
Toralf Förster