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] Startup delay on certain platforms when host-device memory migration is used #2402

Open
1tnguyen opened this issue Nov 21, 2024 · 0 comments

Comments

@1tnguyen
Copy link
Collaborator

On some platforms, when host-device migration is used on the nvidia target (via setting CUDAQ_MAX_CPU_MEMORY_GB), the simulation startup time is delay.

This can be checked by enabling CUDAQ logging, export CUDAQ_LOG_LEVEL=info.

The simulation is stalled after a Create zero initial state line, e.g.,

[2024-11-21 05:55:05.391] [info] [CircuitSimulator.h:913] Allocating 34 new qubits.
[2024-11-21 05:55:05.391] [info] [CusvsimCircuitSimulatorSingleProcess.h:38] [CusvsimSingleProcessCircuitSimulator] Create zero initial state of 34 qubits.

It will eventually finish.

This seems to only occur on certain (platform + driver version) combination.

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

No branches or pull requests

1 participant