From Macro to Micro in C++
summary
Real data shows repeated microsecond spikes traced to container resizing rather than vague "load" issues, backed by added timers and a perf profile that surfaces a rehash call deep in templates. The surprise is the exact bucket sequence: prime bucket sizes, e.g. 389 → 769 rehash that matches the boost::multi_index growth policy, and the diagnosis is concrete — expensive allocations and element rehashing at specific sizes cause the outliers, not algorithmic complexity elsewhere.
AI-written summary · about
chapters (7)
related talks
33mMemory Profiling for Mere Mortals
01h 04mAdvanced .NET debugging techniques from real world investigations
44mObservability Tools C++: Beyond GDB and printf - Tools to Understand the Behavior of Your Program
16mMicroMon: A Monitoring Framework for Tackling Distributed Heterogeneity
30mUnderstanding the runtime behaviors of C++ programs using uftrace tool
26mProfiling Mastery: Decode Your Data and Elevate Observability
32mIs Your Kernel Being Honest? Understanding & measuring low level bottlenecks
25mUse counters to count things
