Difference between revisions of "NorESM code analysis"

From SNIC Documentation
Jump to: navigation, search
(Members)
 
(3 intermediate revisions by 2 users not shown)
Line 3: Line 3:
 
|fields=Climate research
 
|fields=Climate research
 
|financing=SNIC
 
|financing=SNIC
|active=Yes
+
|active=No
 
|start date=2014-10-01
 
|start date=2014-10-01
 
|end date=2014-12-31
 
|end date=2014-12-31
 
}}
 
}}
  
The project aims to understand the performance of the NorESM
+
The [[Media:Juan-camilo_acosta_v2.0.pdf|project aims]] to understand the performance of the NorESM code. We will:
code. We will:
 
 
* Review the MPI pe mapping of the different sub-models (atmosphere, land, sea ice and ocean) currently used for model simulations.
 
* Review the MPI pe mapping of the different sub-models (atmosphere, land, sea ice and ocean) currently used for model simulations.
 
* Analyze the NorESM code to identify code sections and routines to be further evaluated for performance optimization. We will do this by running suitable test cases through analysis tools such as Scalasca and VTune.
 
* Analyze the NorESM code to identify code sections and routines to be further evaluated for performance optimization. We will do this by running suitable test cases through analysis tools such as Scalasca and VTune.
Line 23: Line 22:
 
== Report ==
 
== Report ==
  
The final report with guidelines for performance improvement is submitted to the users
+
The final [[Media:report.pdf|report]] with guidelines for performance improvement is submitted to the users

Latest revision as of 09:31, 13 October 2015

Name NorESM code analysis
Description Complete performance profiling of the Norwegian Earth System Model (NorESM) on Triolith.
Project financing   SNIC
Is active No
Start date 2014-10-01
End date 2014-12-31

The project aims to understand the performance of the NorESM code. We will:

  • Review the MPI pe mapping of the different sub-models (atmosphere, land, sea ice and ocean) currently used for model simulations.
  • Analyze the NorESM code to identify code sections and routines to be further evaluated for performance optimization. We will do this by running suitable test cases through analysis tools such as Scalasca and VTune.
  • Propose a set of recommendations for code optimization changes based on the performance analysis.

Members

 CentreRoleField
Chandan Basu (NSC)NSCApplication expertComputational science

Report

The final report with guidelines for performance improvement is submitted to the users