-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA256
Thank you for your suggestions, Gary.
This is actually not a "real" root server, it's a KVM server (of course). The CPU is an AMD EPYC 7702 with 2 dedicated cores per server@3,35GHz. I chose this server because the bandwith is unmetered and it's a guaranteed 1GHz link. I don't think I will ever be able to relay 125MB/s, but I will try my best. If I can only reach ~50MB/s before the CPU starts to grumble I will set up a second Tor process and a second relay.
I tuned my relay a bit today, using some of the tips from this conversation:
https://lists.torproject.org/pipermail/tor-relays/2010-August/000164.html
It's not really up to date, but still useful to some extent.
Unfortunately I had to restart the Tor process, but my relay was already measured a few times and reaches spikes of 30MB/s. CPU usage is no issue at all yet, there is room for more. I can wait before I get the guard flag, this is not a race...
Thanks again for your help.
All the best.
PGP-Fingerorint: 95C6676453094B229C4EDB34ABA333DFF432E1DD
Elias via tor-relays tor-relays@lists.torproject.org wrote:
This is actually not a "real" root server, it's a KVM server (of course). The CPU is an AMD EPYC 7702 with 2 dedicated cores per server@3,35GHz.
Since this is virtualization, make sure that features such as AES acceleration are active.
The number of cores is not really relevant since Tor is not multi-threaded. The EPYC 7702 can boost up to 3.35 GHz, check that it reaches that under load.
Also since you have 2 cores, you can run two instances of Tor.
I chose this server because the bandwith is unmetered and it's a guaranteed 1GHz link.
I assume you mean 1 Gbit/s.
tor-relays@lists.torproject.org