Skip to content

GitLab

  • Projects
  • Groups
  • Snippets
  • Help
    • Loading...
  • Help
    • Help
    • Support
    • Community forum
    • Submit feedback
    • Contribute to GitLab
  • Sign in
Trac
Trac
  • Project overview
    • Project overview
    • Details
    • Activity
  • Issues 246
    • Issues 246
    • List
    • Boards
    • Labels
    • Service Desk
    • Milestones
  • Operations
    • Operations
    • Metrics
    • Incidents
  • Analytics
    • Analytics
    • Value Stream
  • Wiki
    • Wiki
  • Members
    • Members
  • Collapse sidebar
  • Activity
  • Create a new issue
  • Issue Boards

GitLab is used only for code review, issue tracking and project management. Canonical locations for source code are still https://gitweb.torproject.org/ https://git.torproject.org/ and git-rw.torproject.org.

  • Legacy
  • TracTrac
  • Issues
  • #21758

Closed (moved)
Open
Opened Mar 16, 2017 by Nick Mathewson@nickm🥄

Improve compression estimators for directory spooling

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.

To upload designs, you'll need to enable LFS and have an admin enable hashed storage. More information
Assignee
Assign to
Tor: unspecified
Milestone
Tor: unspecified
Assign milestone
Time tracking
None
Due date
None
Reference: legacy/trac#21758