Do a more detailed performance assessment to identify hotspots
Open
investigation
performance
- Dominant language
- Fortran
- Stars
- 352
- Forks
- 361
- Avg merge
- 2d 21h
- Merged PRs (30d)
- 7
Description
(Task created in NCAR Teamwork 2015-11-11, but still relevant.)
We should do a more detailed performance assessment to identify hotspots. This should include more detailed timers.
In addition, if possible, we should use a tool that identifies cache efficiency, to determine where we are incurring large costs due to cache inefficiencies. (Bill: I feel this is an issue due to (1) the large cost we see of CNZero, and (2) the large cost added when adding 0-weight, inactive columns.)
Contributor guide
Assessment
This issue has not been assessed yet.