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 target: simulation errors when setting CUDAQ_MAX_CPU_MEMORY_GB beyond system memory capacity #2185

Open
3 of 4 tasks
1tnguyen opened this issue Sep 2, 2024 · 0 comments
Labels
bug Something isn't working

Comments

@1tnguyen
Copy link
Collaborator

1tnguyen commented Sep 2, 2024

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

Using the CUDAQ_MAX_CPU_MEMORY_GB environment variable setting, when an unlimited setting (None) is used or a value larger than the actual physical system's memory available, the simulation may fail (e.g., with a cuda error) or produce invalid simulation results.

Steps to reproduce the bug

  • Run a simulation that requires more qubits than GPU memory.

  • Set CUDAQ_MAX_CPU_MEMORY_GB to a value larger than the physical host memory.

Expected behavior

The simulation should work as expected or at least a more descriptive error message should be displayed.

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

Not a regression

Environment

  • CUDA Quantum version: 0.8
  • Python version: 3.10
  • C++ compiler: gcc-11
  • Operating system: Ubuntu 22.04

Suggestions

The current workaround is to set CUDAQ_MAX_CPU_MEMORY_GB to a valid value, taking into account the physical system memory configuration.

@1tnguyen 1tnguyen added the bug Something isn't working label Sep 2, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
bug Something isn't working
Projects
None yet
Development

No branches or pull requests

1 participant