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

Closed (moved)
Open
Opened Jan 12, 2015 by teor@teor

chutney verify: verify in parallel, rather than one at a time (Tor load / performance testing)

There is a need to load-test Tor relays when bringing them up, and to performance-test tor in general, whether relaying or hidden services.

See: Tor BSD Underperformance https://lists.torproject.org/pipermail/tor-dev/2015-January/008048.html Simulate high Tor load https://lists.torproject.org/pipermail/tor-relays/2015-January/006203.html

It would be nice if chutney verify connections were done in parallel, but I don't think that's the case.

Nick, is this SponsorR, or SponsorS, or both?

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#14173