Make your custom .NET GC — "whys" and "hows"

on YouTube ↗57m

" summary

.NET Core exposes Local GC so a custom GC library can replace the runtime GC by setting an environment variable and implementing the GC API (the GC version info and pointers to interfaces, ~75 methods for IGCHeap, handle manager, etc.). A minimal 0 GC uses VirtualAlloc and calloc to return zeroed native memory per object and survives 24k requests but leaks to ~300 MB; a bump-pointer allocator using 16 MiB segments reduces leak to ~200 MB and hits ~600–700 req/s.

AI-written summary · about

" chapters (13)

1. 0:00Intro
2. 0:43Why custom NET GC
3. 6:19Current implementation
4. 9:18Hosting
5. 11:50Tuning
6. 15:17Usage
7. 18:57Implementation
8. 23:43Zero GC
9. 30:45Repository
10. 38:02Bump Pointer
11. 43:46Allocation Contexts
12. 47:11Why it works
13. 51:57Next steps

" related talks

• 57mWriting a custom, real-world .NET GCKonrad Kokosa · DotNext 2019 Piter
• 01h 05mLook Mommy, No GC!Dina Goldshtein · NDC London 2017
• 53mDebugging .NET AppsTess Ferrandez-Norlander · NDC Oslo 2021
• 01h 06m.NET Systems Programming Learned the Hard WayAaron Stannard · NDC Oslo 2023
• 01h 15mCSI .NET – Debugging .NET ApplicationsTess Ferrandez-Norlander · JetBrains .NET Days Online 2021
• 58mManual memory management in .NET FrameworkAdam Furmanek · NDC Porto 2019
• 01h 01mHidden gems in .NET Core 3David Fowler, Damian Edwards · NDC Oslo 2019
• 48mManual Memory Management in .NET FrameworkAdam Furmanek · DevConf 2019