| Anonymous | Login | Signup for a new account | 2013-05-22 19:28 BST | ![]() |
| Main | My View | View Issues | Change Log | Roadmap |
| View Issue Details [ Jump to Notes ] | [ Issue History ] [ Print ] | ||||||||||
| ID | Project | Category | View Status | Date Submitted | Last Update | ||||||
| 0000849 | Xdebug | Feature/Change request | public | 2012-06-02 19:14 | 2012-06-25 19:06 | ||||||
| Reporter | dinu | ||||||||||
| Assigned To | |||||||||||
| Priority | normal | Severity | minor | Reproducibility | always | ||||||
| Status | new | Resolution | open | ||||||||
| Platform | OS | OS Version | |||||||||
| Product Version | |||||||||||
| Target Version | Fixed in Version | ||||||||||
| Summary | 0000849: Decrease tracing/profiling overhead | ||||||||||
| Description | As mentioned, I get 200% to 600% execution timings when tracing a script; is it at all possible to reduce this overhead? Especially since I'm guessing it's roughly linear with the number of function calls, it makes profiling scripts with large number of funcalls difficult. For instance, I have a script that runs under 400ms, but does in excess of 100K calls; this leads to a traced execution time of 2s. The functions at the bottom of the call tree (those that get called a lot) pull a lot of weight for being traced, although execution in a timed cycle shows they don't pulled nearly as much weight as the profile reports. | ||||||||||
| Tags | No tags attached. | ||||||||||
| Operating System | |||||||||||
| PHP Version | 5.3.3 | ||||||||||
| Attached Files | |||||||||||
Issue History |
|||
| Date Modified | Username | Field | Change |
| 2012-06-02 19:14 | dinu | New Issue | |
| 2012-06-25 19:06 | derick | Note Added: 0002279 | |
| Copyright © 2000 - 2011 MantisBT Group |