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
  • Activity
  • Create a new issue
  • Issue Boards
Collapse sidebar

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

Closed
Open
Opened Nov 14, 2004 by weasel (Peter Palfrader)@weasel

client 'flush' takes too much memory

[Moved from bugzilla] Reporter: qumqats@outel.org (Joel M. Baldwin) Description: Opened: 2003-09-19 13:43

I there any way you can reduce the memory used by by the client 'flush' command?

When I have thousands of messages in my client queue the 'flush' command creates such a large memory footprint that the process causes my system to starts swapping.

------- Additional Comments From Nick Mathewson 2003-11-07 08:18 -------

This should be fixed in 0.0.6 CVS; we now lazy-load queued messages as we flush them. [We still use space proportional to the number of pending messages to compute which messages are going where, but this should now be a few dozen bytes per message, not 32KB per message.]

[Automatically added by flyspray2trac: Operating System: FreeBSD]

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