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

Closed (moved)
Open
Opened Sep 27, 2014 by cypherpunks@cypherpunks

Hidden service Load balancing

If you setup a hidden service on multiple servers then the Tor network will apparently just pick one of those and send 99% of the traffic there leaving the other server(s) sitting there idle doing nothing.

It may in theory be possible that some hidden services who service huge amounts of static data such as http://am4wuhz3zifexz5u.onion/ would benefit from some kind of load-balance code which would send 33% of the requests to each server if you have 3 of them (each server with a tor-client and a simple http server).

Load-balancing of hidden services is probably something that would require a lot of research into the implications for security and anonymity. I do not expect this bug to be "resolved" any time soon, I just wanted to point out that this would be a nice thing to have.

To upload designs, you'll need to enable LFS and have 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#13268