• Global
  • Configurations
  • Environment Variables
  • Outputs
  • Logs
  • Tools Status
• Summary
• Application
• Functions
• Loops
• Topology
  • lstopo
  • lstopo_PU
  • lstopo_threads

exec - 2025-09-16 16:55:48 - MAQAO 2025.1.2

Help is available by moving the cursor above any symbol or by checking MAQAO website.

Global Metrics

Total Time (s)		180.32
Max (Thread Active Time) (s)		177.05
Average Active Time (s)		156.60
Activity Ratio (%)		87.0
Average number of active threads		166.748
Affinity Stability (%)		98.6
Time in analyzed loops (%)		58.6
Time in analyzed innermost loops (%)		56.6
Time in user code (%)		58.8
Compilation Options Score (%)		66.7
Array Access Efficiency (%)		53.2
Potential Speedups
Perfect Flow Complexity		1.91
Perfect OpenMP/MPI/Pthread/TBB		1.84
Perfect OpenMP/MPI/Pthread/TBB + Perfect Load Distribution		1.90
No Scalar Integer	Potential Speedup	1.15
	Nb Loops to get 80%	2
FP Vectorised	Potential Speedup	1.32
	Nb Loops to get 80%	3
Fully Vectorised	Potential Speedup	2.09
	Nb Loops to get 80%	4
FP Arithmetic Only	Potential Speedup	1.20
	Nb Loops to get 80%	3

CQA Potential Speedups Summary

Average Active Threads Count⏎

Loop Based Profile⏎

Innermost Loop Based Profile⏎

Application Categorization⏎

Compilation Options⏎

Source Object	Issue
▼exec–
○npair_bin.cpp	-xHost or -march=native should not be used with Intel compilers while targeting (or compiling on) non-Intel processors, use -mavx2
○fix_nve.cpp	-xHost or -march=native should not be used with Intel compilers while targeting (or compiling on) non-Intel processors, use -mavx2
○nbin.cpp	-xHost or -march=native should not be used with Intel compilers while targeting (or compiling on) non-Intel processors, use -mavx2
○pair.cpp	-xHost or -march=native should not be used with Intel compilers while targeting (or compiling on) non-Intel processors, use -mavx2
○pair_eam.cpp	-xHost or -march=native should not be used with Intel compilers while targeting (or compiling on) non-Intel processors, use -mavx2
○nbin_standard.cpp	-xHost or -march=native should not be used with Intel compilers while targeting (or compiling on) non-Intel processors, use -mavx2
○neighbor.cpp	-xHost or -march=native should not be used with Intel compilers while targeting (or compiling on) non-Intel processors, use -mavx2
○domain_omp.cpp	-xHost or -march=native should not be used with Intel compilers while targeting (or compiling on) non-Intel processors, use -mavx2
○atom_vec.cpp	-xHost or -march=native should not be used with Intel compilers while targeting (or compiling on) non-Intel processors, use -mavx2
○compute_temp.cpp	-xHost or -march=native should not be used with Intel compilers while targeting (or compiling on) non-Intel processors, use -mavx2
○comm_brick.cpp	-xHost or -march=native should not be used with Intel compilers while targeting (or compiling on) non-Intel processors, use -mavx2

Loop Path Count Profile⏎

Cumulated Speedup If No Scalar Integer⏎

Cumulated Speedup If FP Vectorized⏎

Cumulated Speedup If Fully Vectorized⏎

Cumulated Speedup If FP Arithmetic Only⏎