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

Closed (moved)
Open
Opened Dec 31, 2014 by teor@teor

IPredator complains that we call time() too much when running over 500Mbps

IPredator writes:

We are constantly testing kernel 3.x vs. the latest 2.6, but noticed that with kernel 3.x beyond 500MBit Tor would spend massive amounts of CPU time on calling time(). On kernel 2.6 we use kernel.vsyscall64=2 which minimizes the impact of constantly doing that.

https://ipredator.se/guide/torserver#performance (JavaScript may be required, unfortunately.)

nickm, is this still an issue? This would be possible to simulate using chutney, right?

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