Skip to content
Haskell Optimization Handbook
⌘ K
Haskell Optimization Handbook

Table of Contents

  • 1. Preliminaries
    • 1.1. How to Use This Book
    • 1.2. Triage
    • 1.3. The Checklist
    • 1.4. The Programs of Consistent Lethargy
    • 1.5. Philosophies of Optimization
    • 1.6. The Golden Rules of Performance-Oriented Haskell
    • 1.7. Setting up a Reproducible Test Environment
    • 1.8. How To Debug
  • 2. Measurement, Profiling, and Observation
    • 2.1. Binary Profiling and Probing
    • 2.2. Thread Level Profiling
    • 2.3. Cmm Probes and Profiling
    • 2.4. Stg and RTS Probes and Profiling
    • 2.5. Core Probes and Profiling
    • 2.6. Haskell Level Probing and Profiling
  • 3. Optimizations
    • 3.1. GHC Flags
    • 3.2. GHC Optimizations
    • 3.3. Library Based Changes
    • 3.4. Library Agnostic Changes
  • 4. Case Studies
    • 4.1. Impact of Seq Removal on SBV’s Internal Cache
    • 4.2. SBV and the Bizarre GHC Regression
    • 4.3. Klister: A First Pass Performance Engineering
    • 4.4. Rearchitecting with Data-Oriented Design
  • Glossary
Haskell Optimization Handbook
/
2. Measurement, Profiling, and Observation
/
2.1. Binary Profiling and Probing

2.1. Binary Profiling and Probing¶

  • 2.1.1. Reading Asm
  • 2.1.2. The Linux time command
  • 2.1.3. The Linux perf utility
    • 2.1.3.1. What is Tables-Next-to-Code
    • 2.1.3.2. So What is the Problem?
    • 2.1.3.3. Assessing the impact of tables-next-to-code
    • 2.1.3.4. How does Tables Next to Code Affect Performance
    • 2.1.3.5. Awards
    • 2.1.3.6. Inspecting with Perf
    • 2.1.3.7. Conclusion
    • 2.1.3.8. Programmatically Consuming Perf Output
    • 2.1.3.9. Helpful One Liners
    • 2.1.3.10. References and Further Reading
    • 2.1.3.11. Footnotes
  • 2.1.4. Dtrace
  • 2.1.5. Valgrind
  • 2.1.6. Using Cachegrind

© 2022-2026, Jeffrey Young (doyougnu) Built with Sphinx 8.2.3