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
Describe the bug
On installing haystack on GPU via pip, faiss-cpu also gets installed. But ideally faiss-gpu should be used on GPU. And deepset/haystack-gpudocker image have same issue as it is using same requirements.txt
Error message
NA
Expected behavior
As stated in #446 , making faiss dependency optional will solve this. Also creating env specific txt file will help user to install additional dependencies like preposed on stackoverflow.
Additional context
NA
To Reproduce
Run on colab or check output of this tutorial
So far we couldn't see significant speed-ups with GPU. From our current understanding, GPU will only help for datasets > 1Mio. Before that, the overhead of copying data to GPU is probably too big. Furthermore, we usually have single queries in the retriever while GPUs rather shine in the case of "batch queries".
In our particular case, we will therefore keep the FAISS CPU version in the docker image because a) typical users will have datasets < 1 Mio docs and b) even for bigger datasets it's currently beneficial to reserve the GPU for the reader (with concurrent API requests we will have better utilization of all available resources).
Therefore, closing this for now. We might do more detailed benchmarking in future.
Describe the bug
On installing haystack on GPU via pip,
faiss-cpu
also gets installed. But ideally faiss-gpu should be used on GPU. Anddeepset/haystack-gpu
docker image have same issue as it is using same requirements.txtError message
NA
Expected behavior
As stated in #446 , making faiss dependency optional will solve this. Also creating env specific txt file will help user to install additional dependencies like preposed on stackoverflow.
Additional context
NA
To Reproduce
Run on colab or check output of this tutorial
System:
The text was updated successfully, but these errors were encountered: