[tor-relays] Issues reaching gigabit relay speeds

teor teor at riseup.net
Fri Nov 1 00:07:33 UTC 2019


Hi,

> On 1 Nov 2019, at 02:44, Mitar <mmitar at gmail.com> wrote:
> 
> On Thu, Oct 31, 2019 at 6:21 AM Matt Traudt <pastly at torproject.org> wrote:
>> - In an ideal world you won't get more load than your fair share.
>> Consider a hypothetically large Tor network with loads of high-capacity
>> relays. Every relay may be capable of 1 Gbps but only see 10 Mbps, yet
>> there is absolutely no problem.
> 
> Thank you. Yes, I understand that if there is more capacity then the
> load will be not fully saturate the available capacity. So it might be
> simply that there are so much relays but not enough exits.
> 
> Then my question is different: how could I test and assure that my
> nodes are able to utilize full gigabit if such demand would be
> required? So that I can assure that they are ready and available? And
> that there is not some other bottleneck somewhere on nodes themselves?

Most tor instances are limited to 200-400 Mbps, because tor is only partly
multithreaded. So you may need to run 3-4 instances to max out a gigabit.

You can run chutney in bandwidth testing mode, to get an idea of the CPU
and RAM limits on your relay:
https://gitweb.torproject.org/chutney.git/tree/README#n98

You might need to adjust CHUTNEY_DATA_BYTES depending on the speed of
your machine. The speed may also be limited by chutney's ability to send
traffic.

If you want to test network speed, you can configure a tor client with:
EntryNodes <your relay fingerprint>
And then download a few very large files at the same time.

T
-------------- next part --------------
A non-text attachment was scrubbed...
Name: signature.asc
Type: application/pgp-signature
Size: 833 bytes
Desc: Message signed with OpenPGP
URL: <http://lists.torproject.org/pipermail/tor-relays/attachments/20191101/e58389b7/attachment.sig>


More information about the tor-relays mailing list