Opened 4 years ago

Last modified 3 years ago

#21758 new enhancement

Improve compression estimators for directory spooling

Reported by: nickm Owned by:
Priority: Low Milestone: Tor: unspecified
Component: Core Tor/Tor Version:
Severity: Normal Keywords: prop278, 031-deferred-20170425, 032-unreached
Cc: ahf Actual Points:
Parent ID: Points: .5
Reviewer: Sponsor: Sponsor4


Once we have zstd compression in place, we should improve the estimated ratio in estimate_compression_ratio(). We could also do well to have that function consider the _size_ of the input data, since bigger data sets compress better.

(I'm deliberately only saying zstd here, not lzma2: We should never do lzma2 compression on the fly, so we shouldn't need to estimate the size of the output for spooling purposes.)

Calling this "low" priority because "0.5" isn't that bad of an estimate.

Child Tickets

Change History (3)

comment:1 Changed 4 years ago by nickm

Parent ID: #21662


comment:2 Changed 4 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 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.