Opened 7 months ago

Last modified 7 months ago

#33775 new defect

sbws measures some relays 100x lower than Torflow

Reported by: teor Owned by:
Priority: High Milestone: sbws: 1.1.x-final
Component: Core Tor/sbws Version:
Severity: Major Keywords: sbws-majority-blocker, sbws-roadmap
Cc: juga Actual Points:
Parent ID: #33121 Points: 2
Reviewer: Sponsor:



I've received multiple reports from relay operators who are concerned their relays are being measured too low.

At the moment, we only have 2 Torflow instances in the network, and 3 sbws instances. So bad sbws measurements can lower any relay's bandwidth, regardless of the Torflow measurement.

Here is one report:

At the moment, the bandwidths are:

moria1 494
maatuska 4
longclaw 5

I have also received a similar report privately from a large relay operator.

This bug could be related to #33009 or #30733.

Child Tickets

#33824newrelay measures low / high on same network and same serverCore Tor/sbws
#33871needs_reviewjugaScale exactly as torflow does?Core Tor/sbws

Change History (5)

comment:1 Changed 7 months ago by teor

Summary: sbws measures some relays 100x less than Torflowsbws measures some relays 100x lower than Torflow

comment:2 Changed 7 months ago by teor

This bug could also be related to #30735.

Also note that:

moria1 and faravahar measure 300-1000 more relays:

And give higher bandwidths for 3700-4200 more relays:

comment:3 Changed 7 months ago by teor

Priority: MediumHigh

These operators have complained about low bandwidths:



5-10% of exit weight
3-25% of exit weight

Some operators are shutting down their relays because of this issue. It's getting really serious.

comment:4 Changed 7 months ago by teor

#33824 has a list of relays with huge measurement differences.

But these relays are all in the same data center:

comment:5 Changed 7 months ago by juga

Parent ID: #33121

Make it child of the ticket to deploy sbws in all bwauths since we can't until this is fixed.

Note: See TracTickets for help on using tickets.