Sign Up to our social questions and Answers Engine to ask questions, answer people’s questions, and connect with other people.
Login to our social questions & Answers Engine to ask questions answer people’s questions & connect with other people.
Lost your password? Please enter your email address. You will receive a link and will create a new password via email.
Please briefly explain why you feel this question should be reported.
Please briefly explain why you feel this answer should be reported.
Please briefly explain why you feel this user should be reported.
I am profiling a PHP application (built upon the Zend framework). Attached you can find a screenshot of the main call graph that KCacheGrind produces from xDebug output.
There are two things that I don’t understand:
1) Why does {main} “fork” into 2 calls? Are they supposed to be parallel somehow or does one happen after the other?
2) The arrow to the left of {main} has a little blue bar with the text 2x; does this mean that the call to Zend_Application->bootstrap happened twice?
The calls (of course) happen after each other. The graph splits because each of the top two functions are called by main(). The graph shows calls, not execution order.
Yes, that’s exactly what it means. main() called Zend_Application->bootstrap twice and ->run once.