...
- switch to the System Monitoring perspective and start the monitor for the machine you'll use before attempting to submit a job with Run Configurations, failure to start the monitor may cause the job submit to error out
- for gcov and gprof, the executable file has to be selected each time you open a .gcno or gmon.* file (this seems to be unique to the synchronized project usage)
The contents of $HOME/.bash_profile should match up with the settings you choose from Project->Properties->C/C++Build->Environment_Management
...
The gmon_shallow.* files can be combined to a summary file with: gmon gprof -s shallow gmon_shallow* . You can also rename a gmon_shallow.NNNNN file to gmon.out to compare the gprof data for one rank with the gmon.sum summary (try to avoid the first PID which is rank zero because it's not as interesting as the others ) .
gcov is not supported at -O3 opt. level
Interesting areas that seem to recur in the timing profile are:
...