You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Running ot.solve with tensors on the CPU allows memory on the GPU (thisis documented in get_backend_list) but also seems to use the GPU, as the Watts are increasing. See attached screencast : Screencast from 08-03-2024 11:24:44.webm
Thanks for the quick reply Cedric, this is happening with the latest dev version :
In [1]: import ot
ot.__version__
In [2]: ot.__version__
Out[2]: '0.9.3dev'
Contrary to #516, the memory consumption starts when calling a function from ot, like dist (when the backend is determined, I guess). Importing ot does not use the GPU indeed.
Describe the bug
Running
ot.solve
with tensors on the CPU allows memory on the GPU (thisis documented inget_backend_list
) but also seems to use the GPU, as the Watts are increasing. See attached screencast :Screencast from 08-03-2024 11:24:44.webm
Is it normal?
Script
The text was updated successfully, but these errors were encountered: