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

nvidia-mgpu simulator is significantly slower than nvidia-fp64 for exp_pauli operations #1543

Closed
3 of 4 tasks
bmhowe23 opened this issue Apr 19, 2024 · 0 comments · Fixed by #1559
Closed
3 of 4 tasks
Assignees
Milestone

Comments

@bmhowe23
Copy link
Collaborator

Required prerequisites

  • Consult the security policy. If reporting a security vulnerability, do not report the bug using this form. Use the process described in the policy to report the issue.
  • Make sure you've read the documentation. Your issue may be addressed there.
  • Search the issue tracker to verify that this hasn't already been reported. +1 or comment there if it has.
  • If possible, make a PR with a failing test to give us a starting point to work on!

Describe the bug

Simulation of quantum programs using exp_pauli are currently more performant on the nvidia and nvidia-fp64 targets than on the nvidia-mgpu backend, even when using a single GPU. There is no good reason for this performance shortfall.

Steps to reproduce the bug

Run the test program here.

Results on my machine are:

Avg Time 10 qubits (nvidia-mgpu) = 1.036675715446472 [sec]
Avg Time 10 qubits (nvidia-fp64) = 0.07855632305145263 [sec]

Expected behavior

The simulation times should be similar or better when using nvidia-mgpu.

Is this a regression? If it is, put the last known working version (or commit) here.

Not a regression

Environment

  • CUDA Quantum version: latest
  • Python version:
  • C++ compiler:
  • Operating system:

Suggestions

We likely need to override applyExpPauli in the nvidia-mgpu simulator.

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

Successfully merging a pull request may close this issue.

1 participant