On 21 Aug 2017, at 14:36, teor teor2345@gmail.com wrote:
On 21 Aug 2017, at 14:05, David Fifield david@bamsoftware.com wrote:
On Mon, Aug 21, 2017 at 01:56:16PM +1000, teor wrote:
On 10 Aug 2017, at 13:36, Roger Dingledine arma@mit.edu wrote:
https://atlas.torproject.org/#details/9695DFC35FFEB861329B9F1AB04C46397020CE... https://atlas.torproject.org/#details/F2044413DAC2E02E3D6BCF4735A19BCA1DE972... https://atlas.torproject.org/#details/BD6A829255CB08E66FBE7D3748363586E46B38... https://atlas.torproject.org/#details/74A910646BCEEFBCD2E874FC1DC997430F9681... https://atlas.torproject.org/#details/7EA6EAD6FD83083C538F44038BBFA077587DD7... all show a big increase in sent bytes starting at the end of July.
It isn't growth in Tor users, since those have stayed relatively flat in the last two weeks.
And the new rate seems to be the new normal -- it's showing no signs of going back to the old rate.
I would assume it's outgoing directory stuff, since that's most of what dir auths do.
Any guesses?
In July, we went from 1% of fallback directory mirrors being down, to about 10% of fallback directory mirrors being down.
See "Fallback Directories Running, Past 90 Days" on: https://consensus-health.torproject.org/graphs.html (Needs JS, SVG)
This means that 10% of client requests go straight to directory authorities. For the other 90%, the first fallback and first directory authority request happen simultaneously, and the authority often wins (and gets to supply the client's first consensus).
Deploying #17750 in 0.3.2 (or backporting it to earlier releases) will fix both these issues:
If we want to reduce the load on authorities, we can backport this change, which makes clients try fallbacks before authorities:
https://trac.torproject.org/projects/tor/ticket/17750
It's been in master (0.3.2) for almost 2 months now.
T -- Tim Wilson-Brown (teor)
teor2345 at gmail dot com PGP C855 6CED 5D90 A0C5 29F6 4D43 450C BA7F 968F 094B ricochet:ekmygaiu4rzgsk6n ------------------------------------------------------------------------