We read every piece of feedback, and take your input very seriously.
To see all available qualifiers, see our documentation.
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
Ability to manually choose when to sync the data to the CPU, so it doesn't sync to CPU after each operation improving performance (raw speed).
The text was updated successfully, but these errors were encountered:
Notes; CPU based funcs could perform a sync check GPU store info about each Vector if it has been synced
Sorry, something went wrong.
suggestion : so if someone says create a vector of size 1000 and fill it 1-1000 you could create a kernel for that
Completed
MPSQUARK
No branches or pull requests
Ability to manually choose when to sync the data to the CPU, so it doesn't sync to CPU after each operation improving performance (raw speed).
The text was updated successfully, but these errors were encountered: