Re: [tor-relays] New round of measuring the accuracy of Tor relays' advertised bandwidth

[Georg Koppen]

Georg Koppen:
> Georg Koppen:
>> Hello!
>>
>> You might recall we ran two "speed tests" so far for investigating the
>> accuracy of a relay's advertised bandwidth, one in 2021[1] and another
>> one earlier this year[2].
>>
>> We gonna pick this test up again this week. However, this time it won't
>> be just a single run but we are rather scheduling the experiment to be
>> on for two weeks and then off for two weeks for the upcoming
>> weeks/months (see: the third item in our network experiments strategy[3]
>> for some rationale). More exactly: we'll run our measurement script for
>> roughly one week, then wait about a week for flooded values leaving the
>> relay descriptors, then 2 weeks off, then starting again...
> 
> A small correction here:
> 
> We'll run the measurement script for roughly *two* weeks, then wait
> about a week for flooded values leaving the relay descriptors, then 1
> week off, then starting again.
> 
> We figured out that's a better use of our resources compared to the two
> weeks break in the measurements cycle.

Another cycle of that experiment started a couple of hours ago.[1] We
hope to have finally figured out all the bugs in our setup so that we
don't see several peaks during our measurement period anymore.[2]

Georg

[1] https://status.torproject.org/experiments/2021-09-23-relay-speed-test/
[2] See:
https://metrics.torproject.org/bandwidth.html?start=2021-05-01=2021-09-23
for how the two measurements look like we did this year.



OpenPGP_signature
Description: OpenPGP digital signature
___
tor-relays mailing list
tor-relays@lists.torproject.org
https://lists.torproject.org/cgi-bin/mailman/listinfo/tor-relays

Re: [tor-relays] Overloaded state indicator on relay-search

[Bleedangel Tor Admin]

My relay was showing as overloaded and I couldn’t figure out why, system utilization was extremely low, only using a tiny bit of ram, network throughout was problem free, I was scratching my head until I realized it shows for 72 hours, and I had been doing a heavy distcc compile on my server one day previous.FYI all, if you show overloaded, it may not be tor, it may be that distcc compiling you did yesterday!On Thu, Sep 23, 2021 at 09:39, Silvia/Hiro  wrote:  Hello all,One of our goals with our current performance work is to reduce theoverload of relays in the network. The implementation of proposal 328[1]a while back made different overload indicators available to relayoperators and since a couple of weeks ago those can be tracked viaOnionoo[2] as well.As we know that a lot of our relay operators use relay search to checkfor the health of their relays, we have launched a new feature there,too, to help them know when their relays are overloaded.When a relay is in the overloaded state we show an amber dot next to therelay nickname.Currently we are counting between 50 and 80 overloaded relays andbetween 10 and 20 overloaded bridges.The overloaded state is reached when one or many of the possible loadmetrics have been triggered. When this happens we show it for 72 hoursafter the relay has recovered [3]. Note, though, that not all of theexposed overload metrics are triggering the overload indicator on relaysearch yet.If you noticed your relay is overloaded, please check the followingsupport article to find out how you can recover to a "normal" state:https://support.torproject.org/relay-operators/relay-bridge-overloaded/Let us known how you find this new feature.Cheers,-hiro[1]https://gitweb.torproject.org/torspec.git/tree/proposals/328-relay-overload-report.md[2]https://lists.torproject.org/pipermail/tor-project/2021-August/003168.html[3] https://gitweb.torproject.org/torspec.git/tree/dir-spec.txt#n637___tor-relays mailing listtor-relays@lists.torproject.orghttps://lists.torproject.org/cgi-bin/mailman/listinfo/tor-relays




publicKey - tor@bleedangel.com - a010c89f.asc
Description: application/pgp-keys


signature.asc
Description: OpenPGP digital signature
___
tor-relays mailing list
tor-relays@lists.torproject.org
https://lists.torproject.org/cgi-bin/mailman/listinfo/tor-relays

[tor-relays] Overloaded state indicator on relay-search

[Silvia/Hiro]

Hello all,

One of our goals with our current performance work is to reduce the
overload of relays in the network. The implementation of proposal 328[1]
a while back made different overload indicators available to relay
operators and since a couple of weeks ago those can be tracked via
Onionoo[2] as well.

As we know that a lot of our relay operators use relay search to check
for the health of their relays, we have launched a new feature there,
too, to help them know when their relays are overloaded.

When a relay is in the overloaded state we show an amber dot next to the
relay nickname.

Currently we are counting between 50 and 80 overloaded relays and
between 10 and 20 overloaded bridges.
The overloaded state is reached when one or many of the possible load
metrics have been triggered. When this happens we show it for 72 hours
after the relay has recovered [3]. Note, though, that not all of the
exposed overload metrics are triggering the overload indicator on relay
search yet.

If you noticed your relay is overloaded, please check the following
support article to find out how you can recover to a "normal" state:

https://support.torproject.org/relay-operators/relay-bridge-overloaded/

Let us known how you find this new feature.

Cheers,
-hiro

[1]
https://gitweb.torproject.org/torspec.git/tree/proposals/328-relay-overload-report.md
[2]
https://lists.torproject.org/pipermail/tor-project/2021-August/003168.html
[3] https://gitweb.torproject.org/torspec.git/tree/dir-spec.txt#n637
___
tor-relays mailing list
tor-relays@lists.torproject.org
https://lists.torproject.org/cgi-bin/mailman/listinfo/tor-relays