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

Closed
Open
Opened Feb 15, 2011 by Karsten Loesing@karsten

Redesign Python parts in Torperf

We're stuffing more and more functionality into Torperf. See #2551 (moved) for outputting circuit build times and #2554 (closed) for adding hidden service time components.

I think it's time to consider a redesign of the Python parts. Having a Python script for writing controller events to disk, a Python script for influencing guard selection, and a cronjob for actually making the requests is already hackish. Adding circuit build times and hidden-service events stretches this even more.

We could have a single Python program that reads from a configuration file what to do, starts Tor, connects to its control port, periodically calls the C program to make requests, and collects all the data we want. This would also make it much easier to set up Torperf.

Sebastian, Mike: Does this make sense?

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