Single profile, multiple libraries

[mstormo]

Not really an issue, but rather a question on functionality, prior to investing time and effort integrating easy_profiler.

We have an application which is plugin/library heavy, and we're looking profiling across library boundaries. How would that work with easy_profiler, and would it be conceivable to add something like categories into the profiling, allowing for easy filtering within a particular library/domain?

For example, our application has an underlying SDK, which would have more low-level blocks, while the application itself would have higher-level blocks. Then the application has plugins, which in themselves would be separate categories.

Obviously, SDK, application and plugins could also just use a prefix convention in the naming of blocks.

Comments, particularly to the usage of easy_profiler across multiple DLL/.so files and main application?

Thanks!

[yse]

Hi. Thank you for feedback and good suggested feature! easy_profiler works good with shared objects (no matter dynamic loaded or dynamic linked). Profiler copy and store informations about blocks in the singleton loaded and unloaded with main application.

GUI tool has a 'Find" tool but unfortunately it's only show matches in the hierarchy. But I think we can add a filter to show only matches. What do you think will be time statistic within own (and parent) category useful?

[yse]

Also you can classify categories by color of the block. It will be nice view in the graph.