Filtering to Minimize Analysis Overhead
Issue
Running your target application with the
can take substantially longer than running your target application without the
.
Intel® Advisor
Intel Advisor
Depending on an accuracy level and analyses you choose for a perspective, different overhead is added to your application execution time.
For example:
Runtime Overhead / Analysis
| Survey
| Characterization
| Dependencies
| MAP
|
---|---|---|---|---|
Target application runtime with
Intel® Advisor compared to runtime without
Intel® Advisor | 1.1x longer
| 2 - 55x longer
| 5 - 100x longer
| 5 - 20x longer
|
Solution
Use the following techniques to skip
uninteresting
modules and/or analyze only
interesting
modules.
Filter Modules
Minimize collection and finalization overhead.
Applicable analyses: Survey,
Characterization with Trip Counts and FLOP collection enabled
.
Use to...
- Exclude modules you cannot optimize, such as third-party code.
- Include a small number of modules of interest.
To implement, do one of the following before/while running the desired analysis:
- Setand identify the modules, where.[Name]is Survey or Trip Counts and FLOP
- Use theadvisorCLI action options--module-filter-mode=excludeand--module-filter=<string>. For example:advisor --collect=survey --project-dir=./myAdvisorProj --module-filter-mode=exclude --module-filter=foo1.so,foo2.so -- ./bin/myTargetApplication
- Setand identify the modules.
- Use theadvisorCLI action options--module-filter-mode=includeand--module-filter=<string>. For example:advisor --collect=survey --project-dir=./myAdvisorProj --module-filter-mode=include --module-filter=foo1.so,foo2.so -- ./bin/myTargetApplication