-
Notifications
You must be signed in to change notification settings - Fork 53
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
scripts for performance tracking system #825
Conversation
I noticed that we have a docs section on benchmarking. Do you think this information needs to be added to docs too? Or is it something that only developers/contributors would be concerned with? |
Correct, this is intended only for internal use (by developers and CI) |
* detect invalid combination * add hermitian versions
POTRFBATCH tests are run with the given precision and sizes | ||
""" | ||
def potrfBatch_suite(*, suite, precision, sizenormal, sizebatch): | ||
fn = 'potrf_batched' |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Other tests test the strided_batched function. Is there a reason POTRF is testing the batched function?
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Yeah, all batch functions in cusolver are strided_batched, but for some reason, potrf is _batched
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
The code reads well, and everything looks good to me. Yet, I am trusting CI to validate this one, as I have not tried the scripts myself.
This PR adds new scripts to generate internal performance reports to track the optimization efforts (see the README file for more details).