| gcc_5 | icx_1 |
|---|---|
[ 3 / 3 ] Host configuration allows retrieval of all necessary metrics. | [ 3 / 3 ] Host configuration allows retrieval of all necessary metrics. |
[ 3.00 / 3 ] Architecture specific option -march=graniterapids is used | [ 2.99 / 3 ] Architecture specific option -x GRANITERAPIDS is used |
[ 3.00 / 3 ] Most of time spent in analyzed modules comes from functions compiled with -g and -fno-omit-frame-pointer -g option gives access to debugging informations, such are source locations. -fno-omit-frame-pointer improve the accuracy of callchains found during the application profiling. | [ 2.99 / 3 ] Most of time spent in analyzed modules comes from functions compiled with -g and -fno-omit-frame-pointer -g option gives access to debugging informations, such are source locations. -fno-omit-frame-pointer improve the accuracy of callchains found during the application profiling. |
[ 0 / 4 ] Application profile is too short (8.46 s) If the overall application profiling time is less than 10 seconds, many of the measurements at function or loop level will very likely be under the measurement quality threshold (0,1 seconds). Rerun to increase runtime duration: for example use a larger dataset or include a repetition loop. | [ 4 / 4 ] Application profile is long enough (11.14 s) To have good quality measurements, it is advised that the application profiling time is greater than 10 seconds. |
[ 2 / 2 ] Application is correctly profiled ("Others" category represents 0.00 % of the execution time) To have a representative profiling, it is advised that the category "Others" represents less than 20% of the execution time in order to analyze as much as possible of the user code | [ 2 / 2 ] Application is correctly profiled ("Others" category represents 0.00 % of the execution time) To have a representative profiling, it is advised that the category "Others" represents less than 20% of the execution time in order to analyze as much as possible of the user code |
[ 3 / 3 ] Optimization level option is correctly used | [ 2.99 / 3 ] Optimization level option is correctly used |
[ 1 / 1 ] Lstopo present. The Topology lstopo report will be generated. | [ 1 / 1 ] Lstopo present. The Topology lstopo report will be generated. |
| gcc_5 | icx_1 |
|---|---|
[ 3 / 4 ] CPU activity is below 90% (85.53%) CPU cores are idle more than 10% of time. Threads supposed to run on these cores are probably IO/sync waiting. Some hints: use faster filesystems to read/write data, improve parallel load balancing and/or scheduling. | [ 4 / 4 ] CPU activity is good CPU cores are active 97.85% of time |
[ 4 / 4 ] Affinity is good (99.49%) Threads are not migrating to CPU cores: probably successfully pinned | [ 4 / 4 ] Affinity is good (99.38%) Threads are not migrating to CPU cores: probably successfully pinned |
[ 4 / 4 ] Enough time of the experiment time spent in analyzed loops (90.12%) If the time spent in analyzed loops is less than 30%, standard loop optimizations will have a limited impact on application performances. | [ 4 / 4 ] Enough time of the experiment time spent in analyzed loops (76.10%) If the time spent in analyzed loops is less than 30%, standard loop optimizations will have a limited impact on application performances. |
[ 0 / 3 ] Cumulative Outermost/In between loops coverage (80.23%) greater than cumulative innermost loop coverage (9.89%) Having cumulative Outermost/In between loops coverage greater than cumulative innermost loop coverage will make loop optimization more complex | [ 0 / 3 ] Cumulative Outermost/In between loops coverage (53.03%) greater than cumulative innermost loop coverage (23.08%) Having cumulative Outermost/In between loops coverage greater than cumulative innermost loop coverage will make loop optimization more complex |
[ 3 / 4 ] A significant amount of threads are idle (22.67%) On average, more than 10% of observed threads are idle. Such threads are probably IO/sync waiting. Some hints: use faster filesystems to read/write data, improve parallel load balancing and/or scheduling. | [ 4 / 4 ] Threads activity is good On average, more than 90.41% of observed threads are actually active |
[ 2 / 2 ] Less than 10% (0.00%) is spend in BLAS2 operations BLAS2 calls usually could make a poor cache usage and could benefit from inlining. | [ 2 / 2 ] Less than 10% (0.00%) is spend in BLAS2 operations BLAS2 calls usually could make a poor cache usage and could benefit from inlining. |
[ 0 / 4 ] Too little time of the experiment time spent in analyzed innermost loops (9.89%) If the time spent in analyzed innermost loops is less than 15%, standard innermost loop optimizations such as vectorisation will have a limited impact on application performances. | [ 4 / 4 ] Enough time of the experiment time spent in analyzed innermost loops (23.08%) If the time spent in analyzed innermost loops is less than 15%, standard innermost loop optimizations such as vectorisation will have a limited impact on application performances. |
[ 3 / 3 ] Less than 10% (0.00%) is spend in BLAS1 operations It could be more efficient to inline by hand BLAS1 operations | [ 3 / 3 ] Less than 10% (0.00%) is spend in BLAS1 operations It could be more efficient to inline by hand BLAS1 operations |
[ 2 / 2 ] Less than 10% (0.00%) is spend in Libm/SVML (special functions) | [ 2 / 2 ] Less than 10% (0.00%) is spend in Libm/SVML (special functions) |
[ 4 / 4 ] Loop profile is not flat At least one loop coverage is greater than 4% (79.82%), representing an hotspot for the application | [ 4 / 4 ] Loop profile is not flat At least one loop coverage is greater than 4% (52.64%), representing an hotspot for the application |
| Analysis | r_1 | r_2 | |
|---|---|---|---|
| Loop Computation Issues | Presence of expensive FP instructions | 2 | 1 |
| Presence of a large number of scalar integer instructions | 2 | 4 | |
| Low iteration count | 0 | 1 | |
| Control Flow Issues | Presence of calls | 1 | 0 |
| Presence of 2 to 4 paths | 1 | 2 | |
| Presence of more than 4 paths | 5 | 1 | |
| Non-innermost loop | 6 | 2 | |
| Low iteration count | 0 | 1 | |
| Data Access Issues | Presence of constant non-unit stride data access | 2 | 3 |
| Presence of indirect access | 0 | 2 | |
| More than 10% of the vector loads instructions are unaligned | 0 | 6 | |
| Presence of special instructions executing on a single port | 0 | 2 | |
| More than 20% of the loads are accessing the stack | 4 | 3 | |
| Vectorization Roadblocks | Presence of calls | 1 | 0 |
| Presence of 2 to 4 paths | 1 | 2 | |
| Presence of more than 4 paths | 5 | 1 | |
| Non-innermost loop | 6 | 2 | |
| Presence of constant non-unit stride data access | 2 | 3 | |
| Presence of indirect access | 0 | 2 | |
| Inefficient Vectorization | Presence of special instructions executing on a single port | 0 | 2 |