Opened 4 months ago

Last modified 4 months ago

#31006 new enhancement

Investigate why timeouts of clients requesting consensuses have recently gone up a lot

Reported by: karsten Owned by: metrics-team
Priority: Medium Milestone:
Component: Metrics/Analysis Version:
Severity: Normal Keywords:
Cc: metrics-team Actual Points:
Parent ID: Points:
Reviewer: Sponsor:

Description

Last week we have been looking at possible reasons for the recent increase in user numbers. One thing we found, which might be unrelated, is that timeouts of clients requesting consensuses have recently gone up a lot. I'm attaching a graph that plots sums of completed downloads, timeouts, and ongoing downloads contained in "dirreq-v3-tunneled-dl" lines. This is just a start of an analysis that I couldn't finish last week, so maybe the next step is just crunch more numbers to see whether this has happened before. I'm creating this ticket to speculate about possible reasons and to have a single place to keep track of this work.

Child Tickets

Attachments (2)

2019-06-21-consensus-request-timeouts.png (73.7 KB) - added by karsten 4 months ago.
2019-07-02-dirreq-v3-tunneled-dl.png (73.6 KB) - added by karsten 4 months ago.

Download all attachments as: .zip

Change History (5)

Changed 4 months ago by karsten

comment:1 Changed 4 months ago by karsten

See this graph:


Changed 4 months ago by karsten

comment:2 Changed 4 months ago by karsten

Here's another graph showing directory requests over more than 10 years:


This graph also contains the fraction of timeouts over time (= timeout / (complete + timeout + running)).

Looks like it has happened before that timeouts went up for a period of time before going down again.

I'll leave this ticket assigned to metrics-team, but I'm not sure how to proceed here. Any insights into what else to look at would be appreciated!

comment:3 Changed 4 months ago by teor

The last big timeout was in 2017-2018 during the onion service DoS, so maybe that's happening again.
Or maybe users are being slowed or blocked somehow.

Note: See TracTickets for help on using tickets.