Using MaxAdvertisedBandwidth instead of AccountingMax on relays with a monthly traffic cap
-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA512 Hello. The Tor Project website recommends configuring an accounting period to put relays into hibernation rather than setting a bandwidth limit in the case where a relay has a traffic cap. Wouldn't it be better to adjust MaxAdvertisedBandwidth instead? Setting an accounting period disables DirCache which prevents the relay from being an HSDir or a guard. Unlike RelayBandwidthRate which throttles connections and can adversely impact user experience, MaxAdvertisedBandwidth just tells the dirauths to limit your consensus weight (iirc) so fewer clients choose you. Has anyone experimented with dynamically changing MaxAdvertisedBandwidth based on monthly traffic remaining so that it uses the majority of its monthly traffic limit without going over? Regards, forest -----BEGIN PGP SIGNATURE----- iHUEARYKAB0WIQQtr8ZXhq/o01Qf/pow+TRLM+X4xgUCauu0VQAKCRAw+TRLM+X4 xqLWAP9BpmWAdp2pT056kFMpg4ecqR6bfXaoJGW6RNiLl0vZRwD/fpR1ef2fjncA bv7YIVXpQGLkWl3vzPGcd7c+Hfyn3w8= =nTfd -----END PGP SIGNATURE-----
participants (1)
-
forest