Skip to content
Snippets Groups Projects
Commit 42d9432b authored by Rafael Ravedutti's avatar Rafael Ravedutti
Browse files

Update target description and remove unnecessary stuff from logbook 


Signed-off-by: default avatarRafael Ravedutti <rafaelravedutti@gmail.com>
parent 8f3e2f86
No related branches found
No related tags found
No related merge requests found
Hide whitespace changes
Inline Side-by-side
Showing
with 1 addition and 162 deletions
log/logbook_RR.md
+ 1
− 162
View file @ 42d9432b
......@@ -58,7 +58,7 @@ Formulate a clear and specific performance target
------------------------------------------------------------------------------>
## Target
Performance analysis of the MD-Bench, a molecular dynamics mini-app based on miniMD. The main goal is to provide a performance model for molecular dynamics and evaluate the performance for different strategies on different targets.
Code generation tool and intermediate representation for particle interactions simulations.
<!-----------------------------------------------------------------------------
## Customer Info
......@@ -80,11 +80,6 @@ All steps required to build the software including dependencies
------------------------------------------------------------------------------>
## How to build software
<!-----------------------------------------------------------------------------
Describe in detail how to configure and setup the testcases(es)
------------------------------------------------------------------------------>
## Testcase description
<!-----------------------------------------------------------------------------
All steps required to run the testcase and control affinity for application
------------------------------------------------------------------------------>
......@@ -94,159 +89,3 @@ All steps required to run the testcase and control affinity for application
<!-----------------------------------------------------------------------------
END BLOCK PREAMBLE
------------------------------------------------------------------------------>
<!-----------------------------------------------------------------------------
START BLOCK ANALYST - This block is required for any new analyst taking over
the project
# Transfer to Analyst: <NAME-TAG>
* Start date: DD/MM/YYYY
* Contact HPC center:
* Name:
* Fon:
* E-Mail:
------------------------------------------------------------------------------>
<!-----------------------------------------------------------------------------
###############################################################################
START BLOCK BENCHMARKING - Run helper script machine-state.sh and store results
in directory session-<ID> named <hostname>.txt. Document everything that you
consider to be relevant for performance.
###############################################################################
------------------------------------------------------------------------------>
## Benchmarking <NAME-TAG>
### Testsystem
* Host/Clustername:
* Cluster Info URL:
* CPU type:
* Memory capacity:
* Number of cores per node:
* Interconnect:
### Software Environment
**Compiler**:
* Vendor:
* Version:
**Libraries**:
* <LIBRARYNAME>:
* Version:
**OS**:
* Distribution:
* Version:
* Kernel version:
<!-----------------------------------------------------------------------------
Create a runtime profile. Which tool was used? How was the profile created.
Describe and discuss the runtime profile.
------------------------------------------------------------------------------>
## Runtime Profile <NAME-TAG>-<ID>
<!-----------------------------------------------------------------------------
Perform a static code review.
------------------------------------------------------------------------------>
## Code review <NAME-TAG>-<ID>
<!-----------------------------------------------------------------------------
Application benchmarking runs. What experiment was done? Add results or
reference plots in directory session-<NAME-TAG>-<ID>. Number all sections
consecutivley such that every section has a unique ID.
------------------------------------------------------------------------------>
## Result <NAME-TAG>-<ID>
### Problem: <DESCRIPTION>
### Measurement <NAME-TAG>-<ID>.1
Example for table:
| NP | runtime |
|----|---------|
| 1 | 2558.89 |
| 2 | 1425.20 |
| 4 | 741.97 |
| 8 | 449.23 |
| 10 | 371.39 |
| 20 | 233.90 |
```
Verbatim Text
```
<!-----------------------------------------------------------------------------
Document the initial performance which serves as baseline for further progress
and is used to compute the achieved speedup. Document exactly how the baseline
was created.
------------------------------------------------------------------------------>
## Baseline
* Time to solution:
* Performance:
<!-----------------------------------------------------------------------------
Explain which tool was used and how the measurements were done. Store and
reference the results. If applicable discuss and explain profiles.
------------------------------------------------------------------------------>
## Performance Profile <NAME-TAG>-<ID>.2
<!-----------------------------------------------------------------------------
Analysis and insights extracted from benchmarking results. Planning of more
benchmarks.
------------------------------------------------------------------------------>
## Analysis <NAME-TAG>-<ID>.3
<!-----------------------------------------------------------------------------
Document all changes with filepath:linenumber and explanation what was changed
and why. Create patch if applicable and store patch in referenced file.
------------------------------------------------------------------------------>
## Optimisation <NAME-TAG>-<ID>.4: <DESCRIPTION>
<!-----------------------------------------------------------------------------
###############################################################################
END BLOCK BENCHMARKING
###############################################################################
------------------------------------------------------------------------------>
<!-----------------------------------------------------------------------------
Wrap up the final result and discuss the speedup.
Optional: Document how much time was spent. A simple python command line tool
for time tracking is [Watson](http://tailordev.github.io/Watson/).
------------------------------------------------------------------------------>
## Summary
* Time to solution:
* Performance:
* Speedup:
## Effort
* Time spent:
<!-----------------------------------------------------------------------------
END BLOCK ANALYST
------------------------------------------------------------------------------>
<!-----------------------------------------------------------------------------
START BLOCK SUMMARY - This block is only required if multiple analysts worked
on the project.
------------------------------------------------------------------------------>
# Overall Summary
* End date: DD/MM/YYYY
## Total Effort
* Total time spent:
* Estimated core hours saved:
<!-----------------------------------------------------------------------------
END BLOCK SUMMARY
------------------------------------------------------------------------------>
0% or .
You are about to add 0 people to the discussion. Proceed with caution.
Please register or to comment