[tor-relays] Bandwidth Fallen Off Drastically

[stealth at nym.mixmin.net]

-----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 at 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 at lists.torproject.org
>
> You can reach the person managing the list at
> 	tor-relays-owner at 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:
>
>    1. Bandwidth Fallen Off Drastically (stealth at nym.mixmin.net)
>    2. Re: Bandwidth Fallen Off Drastically (Daryl Styrk)
>    3. Re: Bandwidth Fallen Off Drastically (s7r)
>    4. Re: Bandwidth Fallen Off Drastically (Sebastian Niehaus)
>    5. Re: Running 5000 relays... (Brian 'redbeard' Harrington)
>
>
> ----------------------------------------------------------------------
>
> Message: 3
> Date: Mon, 14 Mar 2016 19:45:06 +0200
> From: s7r <s7r at sky-ip.org>
> To: tor-relays at lists.torproject.org
> Subject: Re: [tor-relays] Bandwidth Fallen Off Drastically
> Message-ID: <56E6F8A2.5030903 at sky-ip.org>
> Content-Type: text/plain; charset="windows-1252"
>
> Hello,
>
> Your relay seams fine on atlas:
>
> http://atlas777hhh7mcs7.onion/#details/A290A9E71ADFC2FB1C80E64EF851A4B905450105
>
>
> 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.

-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.15 (MingW32)

iQIcBAEBAgAGBQJW5yi+AAoJEH1gNwhiMDZubTgQAJuj6EdfLZsyPsLxfeiLA2nh
w52jJLO3yXg+InJ4IzoSaHzbXsqdUuSmj7RxOsgTr9K1xflX3XkdNmlWYkhs005F
JNMGyglnOb3LlSbJ9fxspZH1KOhwJwy9ZJrHGRqVRXrAC7VBMpJ016TEcFNL3daL
J98LhZuyN5Iecm0k9LhuxoZ0YfnCc03qpkUJDMiM0khsXfoesFWd+Zdss/Igj2aC
mVcE+BMKvO8gHATdVytvHvqqZ07unIAV6mRkw/c/NBqRh07xX6qEJwoDANCEvfS6
7NGQZpgEVWw2lT2GPj5T4WGmEPN6CAfCJTE7fJG1IA1j4iLNgHwRM7kKxQpFWpVa
CAwE8wgc9BxFYCVg8Kzjr/PDJO7mNLFRH3yXXJ9dTo6qS+GRxdZEYTH6FaNc9ERP
W9/hnv18bo0IuQ+o8+sMtzDbAbyyPXDeSbx2qHOzxuTJkzLPkq2t8W2HX5kiurZ8
MIkdkJH+bc71EwV1YBzb/Ca4/kdqTRqEMJzXFtn8wq6fa1uRxDC1S7Su374y4fTy
C1OmTfURhKhK39yVFVJrKqINsgE1GQnKikE2DCMlbrp+IFaItrDOg+gx81mO7WkK
/KbpxnKJotLxIxBX12j0T6CYyGKQio6SSTbI0iObsXJNpEkQCX+jPp3GDDcWPzlK
p/XtNor8MXQS1u96hpwP
=z+T6
-----END PGP SIGNATURE-----