[Author Prev][Author Next][Thread Prev][Thread Next][Author Index][Thread Index]
Re: [tor-relays] Limiting Tor Relay To Run On Google Cloud VPS
This question ties into something I've wondered for a while: Is there a minimum preferred bandwidth rate for relays? I had done some rough calculations a while ago that a $5 VPS from something like Digitalocean could provide approximately 2MiB/s while not exceeding the allotted bandwidth.At that speed, would it be worth adding additional relays?
Friendlyexitnode
‐‐‐‐‐‐‐ Original Message ‐‐‐‐‐‐‐
On Friday, July 19, 2019 3:40 AM, Stephen Mollett <molletts@xxxxxxxxx> wrote:
> Hi,
>
> On 19/07/2019 00:06, Keifer Bly wrote:
>
> > ...as long as the relay generates a maximum of 4.9 GB per
> > month...
>
> A quick back-of-the-envelope calculation gives about 16kbit/sec if you
> spread that bandwidth evenly over the whole month. The only way you
> could do it would be to have a relay that hibernates for the majority of
> the month, "concentrating" that 4.9GB into a day or so then doing
> nothing until the next billing period.
>
> Whether that would really help the network is another matter - I don't
> know how "intermittent" nodes are handled.
>
> Even running a bridge would be challenging when the bandwidth is that
> limited.
>
> (You might be able to game the system by having multiple VPSes and
> moving the node around between them, using a VPN to bring it out at the
> same IP address every time, but that opens a whole new can of worms
> which I don't even want to think about.)
>
> Stephen
>
> tor-relays mailing list
> tor-relays@xxxxxxxxxxxxxxxxxxxx
> https://lists.torproject.org/cgi-bin/mailman/listinfo/tor-relays
_______________________________________________
tor-relays mailing list
tor-relays@xxxxxxxxxxxxxxxxxxxx
https://lists.torproject.org/cgi-bin/mailman/listinfo/tor-relays