Hi everyone, I've read over a couple of other threads regarding relays being slow, however, I can't figure out why mine is running as slow as it is. I used to have a FAST flag and was getting a throughput of several hundred KB/sec on my relay. Now I can't remember if I upgraded TOR or just updated the OS, but I lost the flag. I figured that I'd changed something and would have to 'earn' it again after a few days, week and now months? According to NYX, my average is 6.4KB/sec. I did have the limit set to 1MB and 2MB burst for the last few months thinking that would be more than enough. This morning I changed those (via NYX) to 0 (default) 1GB/s and it looks like it's starting to climb. My internet connection is on a home set up with a connection speed of about 97Mb, so plenty of speed available. If you look at my previous reports on: https://metrics.torproject.org/rs.html#details/9F19251CEE17B1E05084898D164F0... there appears to be a massive drop off in speed during Feb 2019. I'm open to suggestion. Additionally, I'm considering opening an exit port, but everyone seems to say that is a REALLY bad idea on a home set up. Plus I don't really know what I'm doing :)
Hi Ben,
On 4 Apr 2019, at 10:58, Ben Riley <blades1000@gmail.com> wrote:
I've read over a couple of other threads regarding relays being slow, however, I can't figure out why mine is running as slow as it is.
Have you read our wiki page about slow relays? https://trac.torproject.org/projects/tor/wiki/doc/MyRelayIsSlow What do you see when you follow the steps on that page?
I used to have a FAST flag and was getting a throughput of several hundred KB/sec on my relay. Now I can't remember if I upgraded TOR or just updated the OS, but I lost the flag. I figured that I'd changed something and would have to 'earn' it again after a few days, week and now months?
Normally, relays with slow or high-latency connections to North America and Europe won't get used much. Since you're on the other side of the globe, that's inevitable.
According to NYX, my average is 6.4KB/sec. I did have the limit set to 1MB and 2MB burst for the last few months thinking that would be more than enough.
This morning I changed those (via NYX) to 0 (default) 1GB/s and it looks like it's starting to climb.
Setting a limit faster than your connection makes Tor delay or drop packets. Since you already have high latency, drops or delays are going to make your measurements worse.
My internet connection is on a home set up with a connection speed of about 97Mb, so plenty of speed available.
Just use the speed of your connection. (And if it's asymmetric, use the minimum of your upload and download.) Careful with the difference between megabits and megabytes per second!
If you look at my previous reports on:https://metrics.torproject.org/rs.html#details/9F19251CEE17B1E05084898D164F0... there appears to be a massive drop off in speed during Feb 2019. I'm open to suggestion.
Looking at the 5 year graphs, your relay was used when the network was under heavy load for a few months in 2017/2018, and 2018/2019. Now the network isn't overloaded any more, clients don't need your relay as much, so it's back to its usual level.
Additionally, I'm considering opening an exit port, but everyone seems to say that is a REALLY bad idea on a home set up. Plus I don't really know what I'm doing :)
Don't open an exit port at home, unless you like dealing with confused police officers. If you have another IPv4 address, consider setting up a bridge relay. (Bridges on the same IP as relays are easy to censor.) If you don't, try setting up another relay instance on the same IPv4. (There's a limit of two relays per IPv4 address.) T
On Thu, Apr 4, 2019 at 7:06 PM teor <teor@riseup.net> wrote:
Hi Ben,
On 4 Apr 2019, at 10:58, Ben Riley <blades1000@gmail.com> wrote:
I've read over a couple of other threads regarding relays being slow, however, I can't figure out why mine is running as slow as it is.
Have you read our wiki page about slow relays? https://trac.torproject.org/projects/tor/wiki/doc/MyRelayIsSlow
What do you see when you follow the steps on that page?
Bandwidth rate: 1MiB/s Bandwidth burst: 2MiB/s Observed: 485.52 KiB/s
I used to have a FAST flag and was getting a throughput of several hundred KB/sec on my relay. Now I can't remember if I upgraded TOR or just updated the OS, but I lost the flag. I figured that I'd changed something and would have to 'earn' it again after a few days, week and now months?
Normally, relays with slow or high-latency connections to North America and Europe won't get used much. Since you're on the other side of the globe, that's inevitable.
OK, no worries.
According to NYX, my average is 6.4KB/sec. I did have the limit set to 1MB and 2MB burst for the last few months thinking that would be more than enough.
This morning I changed those (via NYX) to 0 (default) 1GB/s and it looks like it's starting to climb.
Setting a limit faster than your connection makes Tor delay or drop packets. Since you already have high latency, drops or delays are going to make your measurements worse.
Maybe this is what I've done in the hope of opening up more bandwidth? I have to admit I'm a little confused by the four options: BandwidthRate - 1GB BandwidthBurst - 1GB RelayBandwidthRate - 1MB RelayBandwidthBurst - 2 MB I find that when I try and change these within NYX by hitting the right arrow and then editing them, that sometimes I go back out to the main screen, hit X twice to reset, that the settings go back. So I've gone in and edited the torrc file directly instead. I've changed those lines to: RelayBandwidthRate 500 KB # Throttle traffic to 100KB/s (800Kbps) RelayBandwidthBurst 600 KB # But allow bursts up to 200KB/s (1600Kbps) Now when I restarted NYX it says: Bandwidth (limit: 500 KB/s, burst: 600 KB/s, measured: 13.0 B/s):
My internet connection is on a home set up with a connection speed of about 97Mb, so plenty of speed available.
Just use the speed of your connection. (And if it's asymmetric, use the minimum of your upload and download.) Careful with the difference between megabits and megabytes per second!
So based on a connection of about 97Mb, which means I can usually peak out my download speeds at 11Mb/sec. Are those speeds above ok? I don't want to drown my connection, but happy to give it a couple of meg :)
If you look at my previous reports on: https://metrics.torproject.org/rs.html#details/9F19251CEE17B1E05084898D164F0... there appears to be a massive drop off in speed during Feb 2019. I'm open to suggestion.
Looking at the 5 year graphs, your relay was used when the network was under heavy load for a few months in 2017/2018, and 2018/2019. Now the network isn't overloaded any more, clients don't need your relay as much, so it's back to its usual level.
OK, that's interesting. I didn't realise the network would change things that much.
Additionally, I'm considering opening an exit port, but everyone seems to say that is a REALLY bad idea on a home set up. Plus I don't really know what I'm doing :)
Don't open an exit port at home, unless you like dealing with confused police officers.
If you have another IPv4 address, consider setting up a bridge relay. (Bridges on the same IP as relays are easy to censor.)
If you don't, try setting up another relay instance on the same IPv4. (There's a limit of two relays per IPv4 address.)
OK, I might leave the exit node alone then :) Thanks Ben.
T _______________________________________________ tor-relays mailing list tor-relays@lists.torproject.org https://lists.torproject.org/cgi-bin/mailman/listinfo/tor-relays
Hello Ben, On 4/4/19 12:59 PM, Ben Riley wrote:
So based on a connection of about 97Mb, which means I can usually peak out my download speeds at 11Mb/sec. Are those speeds above ok? I don't want to drown my connection, but happy to give it a couple of meg :)
just a short note from me, teor alread mentioned it, be careful with Megabit (Mb) vs. MegaByte (MB). Here is the part with the important information: With this option, and in other options that take arguments in bytes, KBytes, and so on, other formats are also supported. Notably, "KBytes" can also be written as "kilobytes" or "kb"; "MBytes" can be written as "megabytes" or "MB"; "kbits" can be written as "kilobits"; and so forth. Tor also accepts "byte" and "bit" in the singular. The prefixes "tera" and "T" are also recognized. If no units are given, we default to bytes. To avoid confusion, we recommend writing "bytes" or "bits" explicitly, since it’s easy to forget that "B" means bytes, not bits. Copied from here: https://2019.www.torproject.org/docs/tor-manual.html.en For you connection it seems to be 97MBit/s, and it gives you a data rate of 11MByte/s, also the important question still is if you have synchronous up- and download bandwidth, please do a speed test if you are not sure -> search engine "speedtest". For the replay bandwidth you have to use the smaller value of both, up- and download capability. Regards yl
So I've edited my torrc file again. My upload and download speeds are different, 11MB/sec down and only about 4MB/sec up. I've set my limits as 3.9MB/s and burst to 4.4MB/s. Just updated the OS, so the machine had to reset. Have to admit it feels like such as waste. It's currently using about 4-6KB/s out of a potential 4,000KB/s..... Something else I did notice in my logs was that for v1 v2 connections, I was initiating 0, but receiving a few, but as the v# went up, to say v4, v5 and v6, those numbers got huge 60,000+ Is that normal? Thanks for the advice and feedback. On Thu, Apr 4, 2019 at 11:59 PM ylms <tor@yl.ms> wrote:
Hello Ben,
On 4/4/19 12:59 PM, Ben Riley wrote:
So based on a connection of about 97Mb, which means I can usually peak out my download speeds at 11Mb/sec. Are those speeds above ok? I don't want to drown my connection, but happy to give it a couple of meg :)
just a short note from me, teor alread mentioned it, be careful with Megabit (Mb) vs. MegaByte (MB).
Here is the part with the important information: With this option, and in other options that take arguments in bytes, KBytes, and so on, other formats are also supported. Notably, "KBytes" can also be written as "kilobytes" or "kb"; "MBytes" can be written as "megabytes" or "MB"; "kbits" can be written as "kilobits"; and so forth. Tor also accepts "byte" and "bit" in the singular. The prefixes "tera" and "T" are also recognized. If no units are given, we default to bytes. To avoid confusion, we recommend writing "bytes" or "bits" explicitly, since it’s easy to forget that "B" means bytes, not bits.
Copied from here: https://2019.www.torproject.org/docs/tor-manual.html.en
For you connection it seems to be 97MBit/s, and it gives you a data rate of 11MByte/s, also the important question still is if you have synchronous up- and download bandwidth, please do a speed test if you are not sure -> search engine "speedtest". For the replay bandwidth you have to use the smaller value of both, up- and download capability.
Regards yl _______________________________________________ tor-relays mailing list tor-relays@lists.torproject.org https://lists.torproject.org/cgi-bin/mailman/listinfo/tor-relays
On 9 Apr 2019, at 12:10, Ben Riley <blades1000@gmail.com> wrote:
So I've edited my torrc file again. My upload and download speeds are different, 11MB/sec down and only about 4MB/sec up. I've set my limits as 3.9MB/s and burst to 4.4MB/s. Just updated the OS, so the machine had to reset. Have to admit it feels like such as waste. It's currently using about 4-6KB/s out of a potential 4,000KB/s.....
Unlike protocols like BitTorrent, which aim for bulk downloads, Tor is a low-latency platform. So Tor tries to give each client a consistently fast, low-latency, high-speed connection. If your relay is slower or higher latency, it won't be used much. (Also, when you change the settings, try to wait a few days for your relay to get its flags back, and the bandwidth usage to stabilise.)
Something else I did notice in my logs was that for v1 v2 connections, I was initiating 0, but receiving a few, but as the v# went up, to say v4, v5 and v6, those numbers got huge 60,000+ Is that normal?
Yes, that's very normal. v1 and v2 aren't used by any supported Tor versions. v3 is used by some old clients that work, but we don't do updates for them any more. T
participants (3)
-
Ben Riley -
teor -
ylms