View Issue Details
|ID||Project||Category||View Status||Date Submitted||Last Update|
|0001670||Xdebug||Profiling||public||2019-05-27 09:59||2021-04-08 11:32|
|Summary||0001670: Allow filtering out source code when profiling|
|Description||When running profiling against a codebase, sometimes the developer might want to filter out (or in) specific parts of the codebase that are of no interest when analyzing the profiling results.|
Example: codebase uses a vendor library that pollutes the profiler output with numerous but performant calls and loops. This makes it hard to find and analyze the developer's own code, without creating a redundant setup where code is generated only to make profiling it simpler.
For instance, I run PHPUnit tests and want to profile my own test cases, not the PHPUnit bootstrapping and boilerplate code.
I am not sure if this is even remotely possible, as I am not versed in how valgrind/callgrind/cachegrind formats work, or how those are implemented in Xdebug. In the end I would love to see a config value similar to
Or should I look into finding tools that operate on finished grind outputs? I know Xdebug has a feature for aggregating multiple dumps into one, so the format should be somewhat workable after profiling runs themselves?
|Tags||No tags attached.|
|2019-05-27 09:59||ojrask||New Issue|
|2019-06-16 00:54||derick||Category||Profiling => Feature/Change request|
|2019-06-16 00:54||derick||Target Version||=> 3.0dev|
|2020-03-12 16:32||derick||Category||Feature/Change request => Profiling|
|2020-09-23 17:00||derick||Target Version||3.0dev =>|
|2021-03-17 09:41||derick||Target Version||=> 3.2dev|