Implementation of Cuda/OpenGL interop output buffers #6
Conversation
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
Owner
|
Hi, it seems like I totally missed this PR! Many thanks! I've just merged the changes. |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
2 participants
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.
Since CUDA Python 11.6 now exposes the OpenGL-CUDA interop API (cupy/cupy#5711), it is now possible to use data sharing for OpenGL examples.
This PR adds support for
CudaOutputBufferType.GL_INTEROPwhen available. This leads to a 90% fps increase forexamples/dynamic_geometry.pywith a 2080Ti (going from 450 fps to 850 fps). As a point of comparison, the Optix provided C++ example runs at 1250 fps with OpenGL-CUDA interop.It also replaces cuda source relative path with absolute paths in examples
hello.py,spheres.pyandtriangle.py.