-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA512
Hello.
Many server providers have a monthly bandwidth limit. It's easy enough
to deal with that by using the AccountingMax option so that Tor will
hibernate when it reaches the bandwidth cap to avoid service suspension.
I run a relay on a provider that, rather than suspending the service,
simply throttles the bandwidth to 10 Mbps until the next month when the
8 TB/month traffic cap is reset. I run through that traffic in just half
a month, so the relay is only operational 50% of the time. But 10 Mbps
is not nothing. What should I do here? I can think of a few options:
1. Set AccountingMax and let the relay hibernate like normal, ensuring
that, whenever it is on, it can achieve maximum performance. The
"free" 10 Mbps bandwidth can then be used for other things, such as
I2P which does not have a ramp-up period.
2. Keep the relay running, relaying up to 1.5 TB/month extra for free,
but with the caveat that the relay suddenly becomes overloaded each
time it reaches the 8 TB mark until the consensus weight falls.
3. Shortly before the bandwidth cap is exceeded, automatically adjust
the torrc to include "MaxAdvertisedBandwidth 10 Mbits", and remove
it when the bandwidth cap resets.
What is a reasonable thing to do here?
Regards,
forest
-----BEGIN PGP SIGNATURE-----
iHUEARYKAB0WIQQtr8ZXhq/o01Qf/pow+TRLM+X4xgUCaY/3wQAKCRAw+TRLM+X4
xtgQAQC2HWAGe7tcmuOGu2v/473IQC9lWHL03lUUpuJPSpGZpwD+LItXaqzV4vPy
phr/rC4LNDZ1AY8m2ZuTzd4MwsVpsgI=
=c+pq
-----END PGP SIGNATURE-----
_______________________________________________
tor-relays mailing list -- [email protected]
To unsubscribe send an email to [email protected]
