Skip to content
GitLab
Projects Groups Snippets
  • /
  • Help
    • Help
    • Support
    • Community forum
    • Submit feedback
    • Contribute to GitLab
  • Sign in
  • Onionbalance Onionbalance
  • Project information
    • Project information
    • Activity
    • Labels
    • Members
  • Repository
    • Repository
    • Files
    • Commits
    • Branches
    • Tags
    • Contributors
    • Graph
    • Compare
  • Issues 8
    • Issues 8
    • List
    • Boards
    • Service Desk
    • Milestones
  • Merge requests 0
    • Merge requests 0
  • CI/CD
    • CI/CD
    • Pipelines
    • Jobs
    • Schedules
  • Deployments
    • Deployments
    • Environments
    • Releases
  • Packages and registries
    • Packages and registries
    • Package Registry
    • Infrastructure Registry
  • 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
  • Core
  • OnionbalanceOnionbalance
  • Issues
  • #3
Closed
Open
Issue created May 21, 2021 by weasel (Peter Palfrader)@weasel

should support balancing many onion addresses

Currently for v3 onion services, onionbalance only can balance a single hostname. As a result, both tor and debian need to run 40-60 onionbalance instances each. That is not cheap on memory use. For instance, a VM with only 6 gigabytes of ram is not able to provide the onionbalance service for debian.

Please make onionbalance be able to balance any number of v3 services.

On top, it'd be nice if it could balance both v3 and v2 at the same time. But that's less of an issue.

Assignee
Assign to
Time tracking