[tor-relays] Consensus Weight low when compared to Advertised Bandwidth

Matt Westfall mwestfall at ecansol.com
Mon Dec 16 18:46:25 UTC 2019


Also you didn't migrate your fingerprint. So it's a new server and will take weeks if not months for the consensus weight to creep up.


-- 
Matt Westfall
President & CIO 
ECAN Solutions, Inc. 
804.592.1672 

On December 16, 2019 1:30:48 PM EST, Neel Chauhan <neel at neelc.org> wrote:
>Hi,
>
>After having my Primcast.com dedicated server suspended, I signed up
>for 
>a dedicated server from Psychz Networks in their Dallas location to run
>
>a FreeBSD-powered Tor exit relay.
>
>https://metrics.torproject.org/rs.html#details/9B6672E247BC4656915DF03A470D4B5BC2E7601F
>
>While Psychz is a bit more expensive than Primcast/ServerRoom (and that
>
>is with an special offer), I get a slightly faster server and far
>better 
>customer support.
>
>One problem is that the consensus weight value is rather low in 
>proportion to the advertised bandwidth value, when they should be 
>approximately similar.
>
>In fact, my server's CPU usage never goes beyond 1%.
>
>Is this normal now that sbws is being deployed? Or is it bad peering on
>
>my relay?
>
>-Neel
>
>===
>
>https://www.neelc.org/
>_______________________________________________
>tor-relays mailing list
>tor-relays at lists.torproject.org
>https://lists.torproject.org/cgi-bin/mailman/listinfo/tor-relays
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.torproject.org/pipermail/tor-relays/attachments/20191216/a3ab7692/attachment.html>


More information about the tor-relays mailing list