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

Closed (moved)
Open
Opened Feb 24, 2015 by Nick Mathewson@nickm🥄

Experiment: does BIO_f_buffer help performance with read/write syscalls?

dgoulet has found that openssl generates lots of small read and write syscalls. Maybe we'd do better to have openssl buffer stuff?

BIO_f_buffer can supposedly help us here. We could buffer reads, writes, or both.

We should see whether this helps performance, whether it causes weird bugs, and so on. We should also try to find out how much memory openssl allocates for this stuff, and take that into account for our OOM calculations.

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