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

Closed
Open
Opened Feb 17, 2013 by Damian Johnson@atagar

Incremental descriptor queries

We presently have a get_server_descriptor() and get_network_status() method, but it's horribly inefficient. Our present messaging infrastructure provided by the BaseController class sends or receives complete messages rather than streaming the message as it comes in. This means that we load the compete "GETINFO desc/all" response into memory before providing our caller with even the first descriptor. This eats up memory and it means an unnecessarily long latency before we provide results. Unfortunately this will take a bit of re-architecting in the BaseController to allow for streamed messages.

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