Opened 3 years ago

Last modified 2 years ago

#21207 new task

Test scenarios for clients that are idle for large periods of time

Reported by: nickm Owned by:
Priority: Medium Milestone: Tor: unspecified
Component: Core Tor/Tor Version:
Severity: Normal Keywords: sponsor4, 031-deferred-20170425, 032-unreached
Cc: Actual Points:
Parent ID: #21205 Points: 3
Reviewer: Sponsor: Sponsor4

Description

See parent ticket for context.

We could use some automated tests that exercise clients in a certain predictable way (as described in the parent ticket), and record the directory bandwidth usage and non-directory bandwidth usage.

I think that we should do this on the real network, and not on a test network: otherwise, there are far too many ways that we can get it wrong.

Child Tickets

Change History (5)

comment:1 Changed 3 years ago by nickm

Sponsor: Sponsor4

Setting "sponsor4" sponsor on all tickets that have the sponsor4 keyword, but have no sponsor set.

comment:2 Changed 3 years ago by nickm

Keywords: 031-deferred-20170425 added
Milestone: Tor: 0.3.1.x-finalTor: 0.3.2.x-final

Triage: batch-defer unowned items of priority Medium or lower to 0.3.2.

comment:3 Changed 3 years ago by arma

I wonder if instrumenting onionperf to record these answers, and then tailoring an onionperf to have each behavior, is a good longer-term (more sustainable) approach here? Since we're going to need to be scripting *something*, and I'd love to have it be the case that whatever we do here, it is easy to do it again periodically to learn if anything's changed.

comment:4 Changed 3 years ago by nickm

Remove Sponsor4 keyword, now that Sponsor4 is the value of the Sponsor field.

comment:5 Changed 2 years ago by nickm

Keywords: 032-unreached added
Milestone: Tor: 0.3.2.x-finalTor: unspecified

Mark a large number of tickets that I do not think we will do for 0.3.2.

Note: See TracTickets for help on using tickets.