Skip to content
GitLab
Projects Groups Topics Snippets
  • /
  • Help
    • Help
    • Support
    • Community forum
    • Submit feedback
    • Contribute to GitLab
  • Sign in
  • S Snowflake
  • Project information
    • Project information
    • Activity
    • Labels
    • Members
  • Repository
    • Repository
    • Files
    • Commits
    • Branches
    • Tags
    • Contributor statistics
    • Graph
    • Compare revisions
  • Issues 93
    • Issues 93
    • List
    • Boards
    • Service Desk
    • Milestones
  • Merge requests 8
    • Merge requests 8
  • CI/CD
    • CI/CD
    • Pipelines
    • Jobs
    • Schedules
  • Deployments
    • Deployments
    • Environments
    • Releases
  • Monitor
    • Monitor
    • Incidents
  • Analytics
    • Analytics
    • Value stream
    • CI/CD
    • Repository
  • Wiki
    • Wiki
  • Snippets
    • Snippets
  • Activity
  • Graph
  • Create a new issue
  • Jobs
  • Commits
  • Issue Boards
Collapse sidebar
  • The Tor Project
  • Anti-censorship
  • Pluggable Transports
  • Snowflake
  • Issues
  • #40179
Closed
Open
Issue created Sep 25, 2022 by David Fifield@dcfOwner

Reduce turbotunnel queueSize from 2048 to 512

After yesterday's deployment of io.Copy memory mitigations (#40177 (closed)), memory use has crept up above 90% again. I recommend implementing the next most effective memory save revealed by profiling: decreasing the turbotunnel queueSize. This is a fixed block of memory that's allocated per connected client.

In dcf/snowflake@328f0f41 I've reduced the parameter from 2048 to 512. I don't know what effect this might have on performance, apart from reducing memory use.

Past discussion about queueSize:

  • https://lists.torproject.org/pipermail/anti-censorship-team/2021-July/000188.html
  • !48 (comment 2744619)
Assignee
Assign to
Time tracking