Hi folks, last week I spent a lot of time trying to get a grasp of traffic server's work flow, and I thought that maybe a call graph would help my understanding.
Here you can find http://blag.esotericsystems.at/igor/hacks/traffic-server/cached_http_forward_req.dot.svg the least terrible output that I've been able to produce semi-automatically: $ sudo callgrind_control --instr=on ; \ curl -x 127.0.0.1:8080 http://www.technologyreview.com/blog/arxiv/27260/ ; \ sudo callgrind_control --instr=off $ ./clean_callgrind.pl callgrind.pid.out > cached_http_forward_req.clean $ ../../jrfonseca.gprof2dot/gprof2dot.py -s -n0 -e0 -f callgrind -o \ cached_http_forward_req.dot cached_http_forward_req.clean $ dot -Tsvg -O cached_http_forward_req.dot I'd like to get some feedback on what else can be safely neglected from this ouptut because it's not useful to understanding the nature of ATS. So long, i References: http://stackoverflow.com/questions/7761448/filter-calls-to-libc-from-valgrinds-callgrind-output/7774742#7774742 http://code.google.com/p/jrfonseca/wiki/Gprof2Dot -- Igor Galić Tel: +43 (0) 664 886 22 883 Mail: i.ga...@brainsware.org URL: http://brainsware.org/ GPG: 571B 8B8A FC97 266D BDA3 EF6F 43AD 80A4 5779 3257
