Please log in to watch this conference skillscast.
Passing by any online Haskell meeting place you'll hear questions about why a program doesn't type check but seldom about why a program is a memory hog. It's widely assumed that the compiler will make your program fast enough and use a reasonable amount of memory.
Whilst this is somewhat true, laziness makes it very easy to introduce space leaks into a program and use more memory than necessary. Therefore it's important to understand the tools and techniques at our disposal for analysing and correcting memory usage.
In this talk, Matthew will explore different ways to analyse the memory usage of programs. Starting with the humble heap profiler, he'll look at its different modes of operation and how to interpret the heap profiles. He'll then discuss some more precise techniques to find space leaks and possible future directions for space profiling.
YOU MAY ALSO LIKE:
Gazing into the Void: Understanding Space (Leaks)
Matthew is a PhD student at the University of Bristol and one of the core GHC contributors. His research interests are in program generation and multi-stage programming.