Skip to content
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.

Sign up for GitHub

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

Jump to bottom

Benchmarking metrics #130

Open
danchitnis opened this issue May 4, 2022 · 0 comments
Open

Benchmarking metrics #130

danchitnis opened this issue May 4, 2022 · 0 comments

Comments

@danchitnis
Copy link

Hello, I noticed that the benchmarking results are often presented using inconsistent metrics, making it hard to compare. For example, the BLAS library is presented in kernel execution time, but the solve library is presented in latency. What is the reason behind using latency as a metric rather than kernel execution time? Does that mean the computation is pipelined and streaming rather than a single execution?
vt-lib-support pushed a commit that referenced this issue May 18, 2023
Squashed 'sparse' changes from 70ab538..bedbdea (#841)
87e7cbe 
bedbdea Merge pull request #130 from liyuanz/update_makefile
165d1dd update
a7c5de2 Merge pull request #129 from liyuanz/next
4942f53 update

Co-authored-by: sdausr <sdausr@xilinx.com>
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
None yet
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
1 participant
@danchitnis