Skip to content
This repository has been archived by the owner on Jul 16, 2019. It is now read-only.

Performance testing harness #1

Open
vchuravy opened this issue Oct 22, 2018 · 3 comments
Open

Performance testing harness #1

vchuravy opened this issue Oct 22, 2018 · 3 comments
Assignees

Comments

@vchuravy
Copy link
Member

  1. Setup a performance testing harness that compares against the base line implementations in Canary.jl
  2. Make it work on Supercloud/Nersc
@vchuravy vchuravy self-assigned this Oct 22, 2018
@vchuravy
Copy link
Member Author

What kind of performance measurements are we interested here? Overall walltime?

@fxgiraldo
Copy link

Valentin, exactly! overall walltime is what we should compare.

@jkozdon
Copy link

jkozdon commented Oct 26, 2018

We could also look at roofline plots. In general, we expect our problems to be bandwidth limited (not flop limited). So, in an ideal world the only cost we'd like to see is the cost of loading and writing memory and all the floating point ops should be hidden.

Whether this is achievable is another question....

We haven't done these calculation yet for our more optimized codes, but this is something we plan to do in the coming weeks to get a sense of how much performance we're leaving on the table.

Personally, I (and maybe all of us at NPS?) have more experience optimizing GPU codes than CPU codes so this will be a good exercise for me/us as well.

Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
None yet
Projects
None yet
Development

No branches or pull requests

3 participants