Opened 8 years ago

Last modified 3 years ago

#8190 new enhancement

Relays should publish number of refill intervals where the token bucket went dry

Reported by: arma Owned by:
Priority: Medium Milestone: Tor: unspecified
Component: Core Tor/Tor Version:
Severity: Normal Keywords: tor-relay metrics statistics bandwidth performance
Cc: robgjansen, karsten, teor Actual Points:
Parent ID: Points:
Reviewer: Sponsor:


Our extrainfo descriptors have 15-minute intervals where we list the sum of bytes handled in that interval.

Intuitively, it seems that congestion should have to do with how many times we run out of tokens in our token bucket.

We could track the number of refills where our global buckets run dry, and publish the number of such refills in each 15-minute interval.

We probably want to track read bucket and write bucket separately; differences between the two might teach us something about #4682 as well.

Child Tickets

Change History (4)

comment:1 Changed 8 years ago by robgjansen

Cc: karsten added

comment:2 Changed 8 years ago by karsten

Sounds doable. Instead of number of refills we could even publish total seconds of a 15-minute interval that a bucket was empty. That's similar to the TB_EMPTY controller events specified in proposal 218. But number of refills would be doable, too.

Would this be global read/write buckets or relay read/write buckets? Buckets of single OR connections wouldn't matter here, I guess?

I can hack on this. But should we finish proposal 218 and get some results from running it in a private Tor network before adding new statistics like the one described here? Most of proposal 218 is already implemented, and I hope to get it merged early into 0.2.5.x.

comment:3 Changed 3 years ago by nickm

Cc: teor added
Keywords: metrics statistics added
Severity: Normal

comment:4 Changed 3 years ago by nickm

Keywords: bandwidth performance added
Note: See TracTickets for help on using tickets.