-
Notifications
You must be signed in to change notification settings - Fork 154
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
Add TESTING.md and BENCHMARKING.md #672
Conversation
reaches its saturation bottleneck, whether that bottleneck is bandwidth or computation. Using data | ||
sets larger than this point is generally not helpful, except in specific cases where doing so | ||
exercises different code and can therefore uncover regressions that smaller benchmarks will not | ||
(this should be rare). |
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.
Do think we should suggest here that benchmarks should only be written for public APIs?
Co-authored-by: H. Thomson Comer <thomcom@gmail.com>
Co-authored-by: H. Thomson Comer <thomcom@gmail.com>
cpp/doc/BENCHMARKING.md
Outdated
In the interest of improving compile time, whenever possible, test source files should be `.cpp` | ||
files because `nvcc` is slower than `gcc` in compiling host code. Note that `thrust::device_vector` | ||
includes device code, and so must only be used in `.cu` files. `rmm::device_uvector`, | ||
`rmm::device_buffer` and the various `column_wrapper` types described in [Testing](TESTING.md) | ||
can be used in `.cpp` files, and are therefore preferred in test code over `thrust::device_vector`. |
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.
Does using NVBench precludes naming the file as cpp
? NVBench header is cuh
.
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.
Never thought about that. Asking.
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.
I think nvbench is .cu only...
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.
Removed this paragraph.
rerun tests |
@gpucibot merge |
This PR mimics rapidsai/cudf#11475 to add libcuspatial's C++ developer guide to the rendered Doxygen HTML docs. See that PR for detailed discussion. Contributes to #598 . Closes #235 Note that this PR depends on #672 and #667 so the changed files will include changes from those PRs until they are merged. Authors: - Mark Harris (https://github.com/harrism) Approvers: - H. Thomson Comer (https://github.com/thomcom) - Vyas Ramasubramani (https://github.com/vyasr) - AJ Schmidt (https://github.com/ajschmidt8) - Michael Wang (https://github.com/isVoid) URL: #673
Description
Contributes to #598. Adds
cpp/doc/TESTING.md
andcpp/doc/BENCHMARKING.md
, the remaining parts of the libcuspatial C++ developer documentation. These documents cover unit testing and unit benchmarking best practices, respectively.Checklist