Opened 5 years ago

Last modified 19 months ago

#13258 new enhancement

Keep stats on effectiveness of consensus diffs

Reported by: Sebastian Owned by:
Priority: Medium Milestone: Tor: unspecified
Component: Core Tor/Tor Version:
Severity: Normal Keywords: tor-relay, metrics, bandwidth, 034-triage-20180328, 034-removed-20180328
Cc: karsten, mvdan, ahf Actual Points:
Parent ID: Points: 3
Reviewer: Sponsor: Sponsor4

Description

We could have all dir mirrors report how many clients they've seen requesting diffs to a consensus X hours old. That way, we could fine-tune the amount of time dir mirrors have to store old diffs, and we could estimate how much of a win they are in general.

Child Tickets

Change History (24)

comment:1 Changed 5 years ago by nickm

Milestone: Tor: 0.2.6.x-finalTor: 0.2.7.x-final
Type: defectenhancement

comment:2 Changed 5 years ago by nickm

Status: newassigned

comment:3 Changed 5 years ago by nickm

Keywords: 027-triaged-1-out added

Marking triaged-out items from first round of 0.2.7 triage.

comment:4 Changed 5 years ago by nickm

Milestone: Tor: 0.2.7.x-finalTor: 0.2.???

Make all non-needs_review, non-needs_revision, 027-triaged-1-out items belong to 0.2.???

comment:5 Changed 4 years ago by nickm

Milestone: Tor: 0.2.???Tor: 0.2.8.x-final

comment:6 Changed 4 years ago by nickm

Points: medium

comment:7 Changed 4 years ago by nickm

Milestone: Tor: 0.2.8.x-finalTor: 0.2.???

It is impossible that we will fix all 252 currently open 028 tickets before 028 releases. Time to move some out. This is my first pass through the "assigned" tickets with no owner, looking for things to move to ???.

If somebody thinks they can get these done before the 0.2.8 timeout, please assign it to yourself and move it back?

comment:8 Changed 3 years ago by arma

Keywords: low-bandwidth added
Severity: Normal

comment:9 Changed 3 years ago by teor

Milestone: Tor: 0.2.???Tor: 0.3.???

Milestone renamed

comment:10 Changed 3 years ago by nickm

Keywords: tor-03-unspecified-201612 added
Milestone: Tor: 0.3.???Tor: unspecified

Finally admitting that 0.3.??? was a euphemism for Tor: unspecified all along.

comment:11 Changed 3 years ago by nickm

Keywords: sponsor4 added

Bulk-adding "sponsor4" keyword to items that would appear to reduce low-bw clients' directory bandwidth usage. But we shouldn't build these without measurement/proposals: see #21205 and #21209.

comment:12 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:13 Changed 2 years ago by nickm

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

comment:14 Changed 2 years ago by nickm

Keywords: tor-03-unspecified-201612 removed

Remove an old triaging keyword.

comment:15 Changed 2 years ago by nickm

Keywords: 027-triaged-in added

comment:16 Changed 2 years ago by nickm

Keywords: 027-triaged-in removed

comment:17 Changed 2 years ago by nickm

Keywords: 027-triaged-1-out removed

comment:18 Changed 2 years ago by nickm

Status: assignednew

Change the status of all assigned/accepted Tor tickets with owner="" to "new".

comment:19 Changed 2 years ago by nickm

Cc: ahf added
Keywords: tor-relay metrics bandwidth added; low-bandwidth sponsor4 removed
Milestone: Tor: unspecifiedTor: 0.3.2.x-final
Points: medium3

comment:20 Changed 2 years ago by nickm

Milestone: Tor: 0.3.2.x-finalTor: 0.3.3.x-final

comment:21 Changed 21 months ago by dgoulet

Milestone: Tor: 0.3.3.x-finalTor: 0.3.4.x-final

comment:22 Changed 19 months ago by nickm

Keywords: 034-triage-20180328 added

comment:23 Changed 19 months ago by nickm

Keywords: 034-removed-20180328 added

Per our triage process, these tickets are pending removal from 0.3.4.

comment:24 Changed 19 months ago by nickm

Milestone: Tor: 0.3.4.x-finalTor: unspecified

These tickets, tagged with 034-removed-*, are no longer in-scope for 0.3.4. We can reconsider any of them, if time permits.

Note: See TracTickets for help on using tickets.