Opened 3 years ago

Closed 3 years ago

#21211 closed task (implemented)

Write and analyze proposals for compressing consensus (diff)s with better algorithms

Reported by: nickm Owned by: ahf
Priority: Medium Milestone: Tor: 0.3.1.x-final
Component: Core Tor/Tor Version:
Severity: Normal Keywords: sponsor4, TorCoreTeam201703
Cc: Actual Points:
Parent ID: #21209 Points: 1
Reviewer: Sponsor: Sponsor4

Description

The idea: Consensus documents are compressed with zlib, but nobody has to compress any given consensus more than once. Therefore, we can safely use more CPU compressing them, and save bandwidth on consensus downloads by switching to something else instead of zlib for consensuses.

This same analysis also applies to consensus diffs.

For this ticket, we should look at the code complexity and potential bandwidth savings here, and decide whether they are worth it.

Child Tickets

Change History (5)

comment:1 Changed 3 years ago by ahf

Owner: set to ahf
Status: newassigned

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

Keywords: TorCoreTeam201703 added

comment:5 Changed 3 years ago by nickm

Resolution: implemented
Status: assignedclosed

ahf wrote this as proposal 278.

Note: See TracTickets for help on using tickets.