rationale Sampling tools like oprofile or dtrace's profile provider don't really provide methods to see what [multithreaded] programs are blocking on - only where they spend CPU time. Though there exist advanced techniques (such as systemtap and dtrace call level probes), it is overkill to build upon that. Poor man doesn't have time. Poor man needs food. method For a poor developer to understand w
![Poor Man's Profiler](https://cdn-ak-scissors.b.st-hatena.com/image/square/0eab8e9cd9dbde3e2fa189db9a856a92255c3755/height=288;version=1;width=512/http%3A%2F%2Fpoormansprofiler.org%2Fpimp.png)