-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1
On Mon, 14 Mar 2016 19:29:58 +0000, you wrote:
Send tor-relays mailing list submissions to tor-relays@lists.torproject.org
To subscribe or unsubscribe via the World Wide Web, visit https://lists.torproject.org/cgi-bin/mailman/listinfo/tor-relays or, via email, send a message with subject or body 'help' to tor-relays-request@lists.torproject.org
You can reach the person managing the list at tor-relays-owner@lists.torproject.org
When replying, please edit your Subject line so it is more specific than "Re: Contents of tor-relays digest..."
Today's Topics:
- Bandwidth Fallen Off Drastically (stealth@nym.mixmin.net)
- Re: Bandwidth Fallen Off Drastically (Daryl Styrk)
- Re: Bandwidth Fallen Off Drastically (s7r)
- Re: Bandwidth Fallen Off Drastically (Sebastian Niehaus)
- Re: Running 5000 relays... (Brian 'redbeard' Harrington)
Message: 3 Date: Mon, 14 Mar 2016 19:45:06 +0200 From: s7r s7r@sky-ip.org To: tor-relays@lists.torproject.org Subject: Re: [tor-relays] Bandwidth Fallen Off Drastically Message-ID: 56E6F8A2.5030903@sky-ip.org Content-Type: text/plain; charset="windows-1252"
Hello,
Your relay seams fine on atlas:
http://atlas777hhh7mcs7.onion/#details/A290A9E71ADFC2FB1C80E64EF851A4B905450...
It has an observed bandwidth of 582.23 KB/s Advertised bandwidth of 512 KB/s and burst 716.8 KB/s
Which is exactly as per your configuration.
The consensus weight is 613, which is totally normal for this value of observed bandwidth.
Tip: if you are on a limited bandwidth plan, better set AccountingMax and do not cap the speed via RelayBandwidthRate / RelayBandwidthBurst. Instead let it run at its maximum speed for less than an entire month rather than capping it to few KB/s to ensure maximum n GB/TB are consumed within a month.
In a previous post someone recommended that I try to reduce my bandwidth to allow my relay to stay active 24/7 x 31 days. This is why I removed the AccountingMax setting and reduced my RelayBandwidthRate to 500kb/s and RelayBandwidthBurst to 700kb/s. What concerns me is that while running arm in graph mode, I rarely see the bandwidth rate steadily flow around 500kb/s.
With a 3tb bandwidth limit per month, following your recommendations, would you recommend that my AccountingMax be set to 55gb per day up and down and turn off RelayBandwidthRate and RelayBandwidthBurst? This will probably mean that the bandwidth will be used up within the first 10-12 hours of each day and my relay will be in hibernation for the remaining portion of that 24 hours. This hibernation period appears to affect the uptime statistics, which means my middle consensus numbers will drop as a consequence. I'm trying to figure out what's the secret sauce here to keep the relay running 24/7 and stay within my 3tb bandwidth limitation.
On Mon, 14 Mar 2016 22:06:24 +0000, stealth@nym.mixmin.net wrote:
RelayBandwidthRate to 500kb/s and RelayBandwidthBurst to 700kb/s. What concerns me is that while running arm in graph mode, I rarely see the bandwidth rate steadily flow around 500kb/s.
My faster relay currently sees somewhat steady traffic, the slower (and older) one that has settings similar to yours has a much more fluctuating bandwidth usage. Continuously pumping 500kB/s in every seconds is not expected, not even every hour.
Andreas
On Mon, 14 Mar 2016 22:06:24 +0000, stealth@nym.mixmin.net wrote: ...
What concerns me is that while running arm in graph mode, I rarely see the bandwidth rate steadily flow around 500kb/s.
It would surprise me if it did. I've posted two graphs on http://blog.apk.li/2016/03/15/tor-relay-traffic.html and these are already smoothed by lumping together several minutes into individual plot points.
But, as you can see, the smaller relay is also losing traffic slowly (it was recently moved to a new host and IP, and was back to the previous traffic pretty fast - within the hour or so).
Andreas
tor-relays@lists.torproject.org
-
Andreas Krey -
stealth＠nym.mixmin.net