GitLab

For every new consensus, Torflow store the descriptors' values in a the database and use them when aggregating/scaling, so it's scaling with last obtained descriptors.

Instead, sbws write those values to the results files at the time the relay is measured and use them when scaling. Therefore, the relays might have updated their descriptors since they were measured.

Since the final weight depends mostly on the relay observed bandwidth, not the measured one, it's penalizing new relays that would have low or 0 observed bandwidth at the time of the measurement, but higher in one day and sbws won't see that in ~4 days.

This would also fix #2550 (moved). A different question would be #28985 (moved).

This can be implemented reading the cached descriptors, to don't have to connect to the control port, because that's done in the scaling part, which is separated from the scanning one.

Thanks @arma for raising this in #tor-dev.