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
  • #8095

Closed
Open
Opened Jan 30, 2013 by Veggie Monster@vmon

Configurable threshold on the overhead of a payload

payload_server should be equipped with a threshold. When chopper asks for a payload for specific chop block, payload_server should checks each available payload candidate upon the block size, computes the resulting overhead and if the overhead exceed the threshold, should be omitted from the list.

Current behaviour is as follows:

payload_server choose randomly N payloads and stops when it finds m payloads all with higher capacity than chopper requested. Then the smallest of this list will be chosen for transmission.

This should be changed in a way that capacity > chopper's requested shouldn't be the only criterion to go on the m-short list but also the overhead should be less than the threshold.

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