The practical trade-off is between writing easy allocated code, and improving it with different methods — which make it harder to write and maintain but putting less pressure to GC. We will consider allocating and deallocating memory as an overhead for some useful job we want use memory for and try to decide what are these trade offs. We will try to derive how GC works from simple performance tests to make it more practical. Yes, it is gonna be Sherlock's detective story, keep your magnifying glass ready!
YOU MAY ALSO LIKE:
- Functional Concurrency in .NET with C# and F# with Riccardo Terrell (Online Course on 28th June - 1st July 2021)
- F# eXchange 2021 (Online Conference on 20th - 21st October 2021)
- Typecheck Your Memory Management with Linear Types (SkillsCast recorded in November 2020)
- Winter is Coming – Even Faster (SkillsCast recorded in November 2020)
Pragmatic Memory Management
Anatoly Zhmur is working with .net from times of early beta in 2001. Now he is Senior Technical Architect doing Bitemporal NoSQL database at Broadridge. He spends a lot of time on optimizing his code to sub milliseconds latencies or multi-gigabyte per second throughputs.