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.

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

[cudauvm] Move conditions to use managed memory #53

Merged
merged 5 commits into from
Jun 2, 2020

Conversation

makortel
Copy link
Collaborator

Part of #43. Kind of equivalent to cms-patatrack/cmssw#157.

By default cudaMemAdvise() and cudaMemPrefetchAsync() are enabled, but there are compile-time switches to disable them.

@makortel
Copy link
Collaborator Author

makortel commented May 29, 2020

Passes tests, but I want to assess performance impact (on V100) first before merging.

@makortel
Copy link
Collaborator Author

makortel commented Jun 2, 2020

Here is a throughput scan on a single V100 (all cases process 400k events / concurrent event, "1 concurrent event" case takes about 9 minutes)

cudauvm_pr53

Conclusions

  • Managed memory gives 0-4 % smaller throughput than explicit memory
  • cudaMemAdvise(cudaMemAdviseSetReadMostly) has a 2-6 % effect until the throughput plateau is reached
    • at the plateau it does not make a difference
  • Prefetch has no impact in this test
    • as expected, conditions data is transferred once and then used many many times

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

Successfully merging this pull request may close these issues.

1 participant