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

Closed (moved)
Open
Opened Sep 01, 2011 by Karsten Loesing@karsten

Investigate memory consumption of metrics-web

Last week, metrics-web on yatei ran out of memory quite often. The reason is probably that we're reading too much stuff from stats/ (in order to avoid parsing stuff twice) without garbage collecting aggressively enough. In particular, stats/archives-import-history and stats/bridge-stats-raw might be problematic.

The workaround was to change max memory from 4G to 8G. This fixes the problem for now, but obviously we can do better.

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