runtime: should there be a minimum heap size to trigger GC? · Issue #9067 · golang/go (original) (raw)

Skip to content

Navigation Menu

• • GitHub Copilot Write better code with AI
  • GitHub Advanced Security Find and fix vulnerabilities
  • Actions Automate any workflow
  • Codespaces Instant dev environments
  • Issues Plan and track work
  • Code Review Manage code changes
  • Discussions Collaborate outside of code
  • Code Search Find more, search less
• Explore
  • Learning Pathways
  • Events & Webinars
  • Ebooks & Whitepapers
  • Customer Stories
  • Partners
  • Executive Insights
• • GitHub Sponsors Fund open source developers
  • The ReadME Project GitHub community articles
• • Enterprise platform AI-powered developer platform
• Pricing

Provide feedback

Saved searches

Use saved searches to filter your results more quickly

Sign up

Appearance settings

Description

The really tiny GCs (of less than 1 MB) are very sensitive to constant overheads in the GC. The usual 2x policy doesn't work great if the program has a consistent live data set of 100 kB. There are tons of GCs and the constants dominate.

Should we set a minimum heap size for GC like 1 MB, so that even if the previous GC ended with 100 kB of live data, we still wait until 1 MB (not 200 kB) before the next one?