Separate Data Collection Using advixe-cl
- Run Survey collection:advixe-cl --collect=survey --auto-finalize --stackwalk-mode=online --static-instruction-mix –-project-dir=<project-dir> -- <target> [target-options]
- Run thecollect.pyscript to mark up specific regions with--markup <markup_type>option. For example, use--markup genericto mark up all regions and select the most profitable for analysis:advixe-python <APM>/collect.py <project-dir> --markup generic
- Run Trip Counts and FLOP collection:advixe-cl --collect=tripcounts --flop --stacks –-enable-cache-simulation --cache-config=<cache-configuration> --enable-data-transfer-analysis --project-dir=<project-dir> -- <target> [target-options]
- [Optional]: Run Dependencies collection. This improves model accuracy but increases analysis overhead. Dependencies collection is not required for analyzing existing parallel regions but strongly recommended for generic analysis, which is the default mode. For example, you can use the following command to run Dependencies collection:advixe-cl –-collect=dependencies --filter-reductions --loop-call-count-limit=16 --project-dir=<project-dir> -- <target> [target-options]
- For multi-process workloads that include a parent script, Python* or other process and a child process with usercode of interest: if you want to analyze a child process, you must additionally specify its name with the--executable-of-interestoption when running the Dependencies collection:advixe-cl --collect=dependencies --executable-of-interest=<child-binary> ...This isnotrequired for the Survey and Trip Counts and FLOP steps because, by default, Survey and Trip Counts and FLOP profile all processes.
- Attaching to a process is possible for Survey, but is not supported by Trip Counts and FLOP and Dependencies collections.
- Usingittnotifymarked-up binaries and launching analysis in a start-paused mode are supported for Survey and Trip Counts and FLOP steps only. For more information, refer to Pause/Resume Collection Using API Methods.