Closed noahlevenson closed 1 year ago
As of this writing, we have disabled the throughput display, which invalidates this ticket. However, on Slack, @woodybury said:
derek and I are thinking of re-introducing throughput in v2 on like an "advanced" view so perhaps just icebox that ticket for latter
Closing for now because advanced stats still aren't a thing yet.
Your widget may acquire some number of stable connections and report "N peers connected" -- but if your connected peers aren't pushing requests through those connections, your widget reports 0 bytes/sec throughput, and you might misinterpret it as being stalled or broken.
When censored peer concurrency > 1, censored peers will try to acquire these idle and unused connections for redundancy.
At some point in the near future, we'll probably write a multipath-y thing wherein all censored users utilize all of their upstream connections in parallel. This would essentially invalidate the topic of this ticket.
It's also possible that we might set censored peer concurrency to 1 for the MVP, which would also invalidate the topic of this ticket.