Skip to content

GitLab

  • Menu
Projects Groups Snippets
    • Loading...
  • Help
    • Help
    • Support
    • Community forum
    • Submit feedback
  • Sign in / Register
  • GHC GHC
  • Project information
    • Project information
    • Activity
    • Labels
    • Members
  • Repository
    • Repository
    • Files
    • Commits
    • Branches
    • Tags
    • Contributors
    • Graph
    • Compare
    • Locked Files
  • Issues 4,837
    • Issues 4,837
    • List
    • Boards
    • Service Desk
    • Milestones
    • Iterations
  • Merge requests 449
    • Merge requests 449
  • CI/CD
    • CI/CD
    • Pipelines
    • Jobs
    • Schedules
    • Test Cases
  • Deployments
    • Deployments
    • Releases
  • Analytics
    • Analytics
    • CI/CD
    • Code review
    • Insights
    • Issue
    • Repository
    • Value stream
  • Wiki
    • Wiki
  • Snippets
    • Snippets
  • Activity
  • Graph
  • Create a new issue
  • Jobs
  • Commits
  • Issue Boards
Collapse sidebar
  • Glasgow Haskell Compiler
  • GHCGHC
  • Issues
  • #20391

Closed
Open
Created Sep 19, 2021 by Orpheus@orpheus-antpool

Trigger garbage collection on external signal

Motivation

For memory-intensive applications, GHC garbage collection is frequently lagging behind new allocations, leading to a constant increase in memory utilization that is not released back to the OS.

Proposal

Enable the garbage collector to listen to an external signal (e.g. SIGUSR1), which would trigger a thorough cleanup and memory compaction, releasing the memory to the OS. Without this capability, long-running services have to be periodically restarted to maintain high performance, but this causes downtime (which is typically expected to be orders of magnitude higher than the downtime caused by a thorough GC).

To upload designs, you'll need to enable LFS and have an admin enable hashed storage. More information
Assignee
Assign to
Time tracking