Difference between revisions of "NEMO3D"
(New page: =NEMO3D Performance Evaluation= This is a summary of the performance evaluation of NEMO3D. Our initial focus was on finding hot spots in the code where most of the computational work is be...) |
|||
| Line 1: | Line 1: | ||
| − | + | This is a summary of the performance evaluation of NEMO3D. Our initial focus was on finding hot spots in the code where most of the computational work is being done. | |
| − | This is a summary of the performance evaluation of NEMO3D. Our initial focus was on finding hot spots in the code where most of the computational work is being done. We have found two loops in the source file "h_cvectr_multi.c" | + | |
| + | ==Instrumentation overhead== | ||
| + | |||
| + | |||
| + | We have found two loops in the source file "h_cvectr_multi.c" that together account for about 90% (with 16 processors) of the runtime of the NEMO3D application. Loop 1 is | ||
Revision as of 18:07, 3 September 2008
This is a summary of the performance evaluation of NEMO3D. Our initial focus was on finding hot spots in the code where most of the computational work is being done.
Instrumentation overhead
We have found two loops in the source file "h_cvectr_multi.c" that together account for about 90% (with 16 processors) of the runtime of the NEMO3D application. Loop 1 is
