You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
The PR adds CUPTI Activity API to measure GPU active time instead of CUDA events.
CUPTI timing can be enable with the optional command line option --cupti-timer.
The main advantage of CUPTI is that it measures the actual GPU active time, excluding noise, such as kernel launch latency and host activities (e.g. cuda driver). This also makes the measurements independent from the CPU speed or driver version.
Other advantages are:
0.5us granularity
No blocking kernel: a more realistic measurement of the CPU time.
Consistency with Nvidia profiling tools.
Functionalities that run on different streams concurrently are correctly measured (not double-counted).
The busy GPU time accounting may change computed throughput significantly. We still divide element and byte counts by GPU time. With CUPTI, these become rates per second of GPU activity. They can remain high even when long gaps between activities make application throughput poor.
The NVBench printers (particularly, json_printer) do not reflect which timer was used making it difficult to automatically compare against event-based benchmarking result.
Python package is presently build with NVBench_ENABLE_CUPTI=OFF because of a longstanding and gaining opinion that use of CUPTI is to be phased out.
The NVBench printers (particularly, json_printer) do not reflect which timer was used making it difficult to automatically compare against event-based benchmarking result.
I definitely agree. We cannot compare two different methodology. I introduced the comparison script version and annotated the json with the timing methodology. If script versions are not compatible or timing methods are different, it raises an error.
Also, I tried to organize each fix in a separate commit to help for the review
This branch has not been deployed
No deployments
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Fixes #184
The PR adds CUPTI Activity API to measure GPU active time instead of CUDA events.
CUPTI timing can be enable with the optional command line option
--cupti-timer.The main advantage of CUPTI is that it measures the actual GPU active time, excluding noise, such as kernel launch latency and host activities (e.g. cuda driver). This also makes the measurements independent from the CPU speed or driver version.
Other advantages are:
Example
nvbench.example.cpp17.throughputon an RTX A6000:--cupti-timer