<html><head></head><body><div class="ydpd1760991yahoo-style-wrap" style="font-family:Helvetica Neue, Helvetica, Arial, sans-serif;font-size:16px;"><div></div>
<div>Hi All!</div><div><br></div><div>Curious... What are the magic numbers (i.e., max timeout, reoccurrence, etc) that earn a relay overloaded status?</div><div><br></div><div>I'm trying to tune my portion of the Tor network and finding that sweet spot has proven elusive.</div><div><br></div><div>Thanks!</div><div><br></div><div><br></div><div>Gary</div><div><br></div><div><br></div>
<div id="ydpd1760991yahoo_quoted_2692268929" class="ydpd1760991yahoo_quoted">
<div style="font-family:'Helvetica Neue', Helvetica, Arial, sans-serif;font-size:13px;color:#26282a;">
<div>
On Friday, September 24, 2021, 3:48:18 AM MDT, Silvia/Hiro <hiro@torproject.org> wrote:
</div>
<div><br></div>
<div><br></div>
<div><div dir="ltr"><br clear="none"><br clear="none">On 9/23/21 10:54 PM, friendlyexitnode via tor-relays wrote:<br clear="none">> This looks like an awesome feature! I super appreciate it.<br clear="none">> <br clear="none">> Random question though (and I'm the first to admit I may be doing something wrong), I notice that on Mobile it says my relays are overloaded however when I view it on a normal computer I don't get the overloaded indicator. I've tried refreshing multiple times but getting the same results. Is anyone seeing the same thing?<br clear="none"><br clear="none"><br clear="none">Hi,<br clear="none"><br clear="none">could you let me know when you accessed the page via mobile approximately?<br clear="none"><br clear="none">I'll try to check if any of your relays were overloaded in the past.<br clear="none">When a node is overloaded the state is kept for 72 hours.<br clear="none"><br clear="none">Cheers,<br clear="none">-hiro<br clear="none"><br clear="none">> <br clear="none">> Family Members:<br clear="none">> F01E382DA524A57F2BFB3C4FF270A23D5CD3311D<br clear="none">> 623CCCC1A1370700DD03046A85D953D35CAB5C21<br clear="none">> F9A28AB71D7E4E446308641A556EA53BA55FCB50<br clear="none">> 23F74D581DE92AC59D3527DE4D448E036139D81E<br clear="none">> A00E900534DFF76371064C03714753EAF8B88820<br clear="none">> C232D8EE677E6BDF5CFFDDCAC4E2B1682DCE7AE5<br clear="none">> <br clear="none">> - The Friendly Exit Node Family<br clear="none">> <br clear="none">> Sent with ProtonMail Secure Email.<br clear="none">> <br clear="none">> ‐‐‐‐‐‐‐ Original Message ‐‐‐‐‐‐‐<br clear="none">> <br clear="none">> On Thursday, September 23rd, 2021 at 8:39 AM, Silvia/Hiro <<a shape="rect" href="mailto:hiro@torproject.org" rel="nofollow" target="_blank">hiro@torproject.org</a>> wrote:<br clear="none">> <br clear="none">>> Hello all,<br clear="none">>><br clear="none">>> One of our goals with our current performance work is to reduce the<br clear="none">>><br clear="none">>> overload of relays in the network. The implementation of proposal 328[1]<br clear="none">>><br clear="none">>> a while back made different overload indicators available to relay<br clear="none">>><br clear="none">>> operators and since a couple of weeks ago those can be tracked via<br clear="none">>><br clear="none">>> Onionoo[2] as well.<br clear="none">>><br clear="none">>> As we know that a lot of our relay operators use relay search to check<br clear="none">>><br clear="none">>> for the health of their relays, we have launched a new feature there,<br clear="none">>><br clear="none">>> too, to help them know when their relays are overloaded.<br clear="none">>><br clear="none">>> When a relay is in the overloaded state we show an amber dot next to the<br clear="none">>><br clear="none">>> relay nickname.<br clear="none">>><br clear="none">>> Currently we are counting between 50 and 80 overloaded relays and<br clear="none">>><br clear="none">>> between 10 and 20 overloaded bridges.<br clear="none">>><br clear="none">>> The overloaded state is reached when one or many of the possible load<br clear="none">>><br clear="none">>> metrics have been triggered. When this happens we show it for 72 hours<br clear="none">>><br clear="none">>> after the relay has recovered [3]. Note, though, that not all of the<br clear="none">>><br clear="none">>> exposed overload metrics are triggering the overload indicator on relay<br clear="none">>><br clear="none">>> search yet.<br clear="none">>><br clear="none">>> If you noticed your relay is overloaded, please check the following<br clear="none">>><br clear="none">>> support article to find out how you can recover to a "normal" state:<br clear="none">>><br clear="none">>> <a shape="rect" href="https://support.torproject.org/relay-operators/relay-bridge-overloaded/" rel="nofollow" target="_blank">https://support.torproject.org/relay-operators/relay-bridge-overloaded/</a><br clear="none">>><br clear="none">>> Let us known how you find this new feature.<br clear="none">>><br clear="none">>> Cheers,<br clear="none">>><br clear="none">>> -hiro<br clear="none">>><br clear="none">>> [1]<br clear="none">>><br clear="none">>> <a shape="rect" href="https://gitweb.torproject.org/torspec.git/tree/proposals/328-relay-overload-report.md" rel="nofollow" target="_blank">https://gitweb.torproject.org/torspec.git/tree/proposals/328-relay-overload-report.md</a><br clear="none">>><br clear="none">>> [2]<br clear="none">>><br clear="none">>> <a shape="rect" href="https://lists.torproject.org/pipermail/tor-project/2021-August/003168.html" rel="nofollow" target="_blank">https://lists.torproject.org/pipermail/tor-project/2021-August/003168.html</a><br clear="none">>><br clear="none">>> [3] <a shape="rect" href="https://gitweb.torproject.org/torspec.git/tree/dir-spec.txt#n637" rel="nofollow" target="_blank">https://gitweb.torproject.org/torspec.git/tree/dir-spec.txt#n637</a><br clear="none">>><br clear="none">>> tor-relays mailing list<br clear="none">>><br clear="none">>> <a shape="rect" href="mailto:tor-relays@lists.torproject.org" rel="nofollow" target="_blank">tor-relays@lists.torproject.org</a><br clear="none">>><br clear="none">>> <a shape="rect" href="https://lists.torproject.org/cgi-bin/mailman/listinfo/tor-relays" rel="nofollow" target="_blank">https://lists.torproject.org/cgi-bin/mailman/listinfo/tor-relays</a><div class="ydpd1760991yqt5260897854" id="ydpd1760991yqtfd70500"><br clear="none">> _______________________________________________<br clear="none">> tor-relays mailing list<br clear="none">> <a shape="rect" href="mailto:tor-relays@lists.torproject.org" rel="nofollow" target="_blank">tor-relays@lists.torproject.org</a><br clear="none">> <a shape="rect" href="https://lists.torproject.org/cgi-bin/mailman/listinfo/tor-relays" rel="nofollow" target="_blank">https://lists.torproject.org/cgi-bin/mailman/listinfo/tor-relays</a><br clear="none">> <br clear="none">_______________________________________________<br clear="none">tor-relays mailing list<br clear="none"><a shape="rect" href="mailto:tor-relays@lists.torproject.org" rel="nofollow" target="_blank">tor-relays@lists.torproject.org</a><br clear="none"><a shape="rect" href="https://lists.torproject.org/cgi-bin/mailman/listinfo/tor-relays" rel="nofollow" target="_blank">https://lists.torproject.org/cgi-bin/mailman/listinfo/tor-relays</a><br clear="none"></div></div></div>
</div>
</div></div></body></html>