Analyze Performance After Optimization
In this step, run the Performance Snapshot analysis again to profile the application with loop interchange enabled.
To see the improvement provided by using the loop interchange technique, run the Performance Snapshot analysis again.
Depending on your compiler and IDE, when configuring the analysis, you may need to browse to a different executable that was generated during recompilation in the previous step.
Once the sample application finishes, the Performance Snapshot Summary window opens.
Observe these main indicators:
The Elapsed Time for the application is significantly reduced. This improvement is mainly the result of the eliminated memory access bottleneck, which caused the processor to frequently miss the cache and request data from the DRAM, which is very expensive in terms of latency.
The Vectorization metric is equal to 0.0%, which means that the code was not vectorized. Due to this, Performance Snapshot highlights the HPC Performance Characterization analysis as a potential next step.
In this case, the code was not vectorized because the Intel® oneAPI DPC++/C++ Compiler does not perform vectorization when compiling with binary size favored (-O1).
To enable automatic vectorization by the compiler, follow these steps:
Open the Makefile located in ../matrix/linux folder with a text editor.
Change line 42 from:
CFLAGS = -g -O1
CFLAGS = -g -O2
Run the following command to recompile the application:
Next step: Analyze Vectorization Efficiency.
Did you find the information on this page useful?