Skip to content

GitLab

  • Menu
Projects Groups Snippets
    • Loading...
  • Help
    • Help
    • Support
    • Community forum
    • Submit feedback
  • Sign in / Register
  • B baobaxia
  • Project information
    • Project information
    • Activity
    • Labels
    • Members
  • Repository
    • Repository
    • Files
    • Commits
    • Branches
    • Tags
    • Contributors
    • Graph
    • Compare
  • Issues 67
    • Issues 67
    • List
    • Boards
    • Service Desk
    • Milestones
  • Merge requests 0
    • Merge requests 0
  • CI/CD
    • CI/CD
    • Pipelines
    • Jobs
    • Schedules
  • Deployments
    • Deployments
    • Environments
    • Releases
  • Monitor
    • Monitor
    • Incidents
  • Packages & Registries
    • Packages & Registries
    • Package Registry
    • Infrastructure Registry
  • Analytics
    • Analytics
    • Value stream
    • CI/CD
    • Repository
  • Wiki
    • Wiki
  • External wiki
    • External wiki
  • Snippets
    • Snippets
  • Activity
  • Graph
  • Create a new issue
  • Jobs
  • Commits
  • Issue Boards
Collapse sidebar
  • NPDD
  • baobaxia
  • Issues
  • #148

Closed
Open
Created May 04, 2015 by Vince Tozzi@vinceOwner

Performance/memory leak

Created by: agger-magenta

The last couple of days I've seen huge problems on hyndla due to an apparently runaway "beam.smp".

Basically, it uses huge amounts of memory and causes basic git and FS access operations to take very long time. This occurs also when the process is idle (e.g., process_requests is not being run).

There might be a solution here: http://stackoverflow.com/questions/25162484/rabbitmq-beam-smp-and-high-cpu-memory-load-issue

Assignee
Assign to
Time tracking

Data Center Comunitário Livre - DCCL