Originally created by @gaby on GitHub (Apr 10, 2025).
### Check Existing Issues
- [x] I have searched the existing issues and discussions.
### Problem Description
Currently the communication to Qdrant relies on HTTP. You can get higher throughput by using gRPC with Qdrant.
### Desired Solution you'd like
This is already supported by the Library used by OpenWebUI. It requires a boolean field and a port.
See here: https://github.com/qdrant/qdrant-client?tab=readme-ov-file#grpc
Related code: https://github.com/open-webui/open-webui/blob/dev/backend/open_webui/retrieval/vector/dbs/qdrant.py#L24
### Alternatives Considered
None
### Additional Context
_No response_
@gaby commented on GitHub (Apr 10, 2025):
How many config options should be added for this?
- QDRANT_GRPC: bool
- QDRANT_GRPC_HOST: str
- QDRANT_GRPC_PORT: int
Do those make sense?
Blocking a user prevents them from interacting with repositories, such as opening or commenting on pull requests or issues. Learn more about blocking a user.
Originally created by @gaby on GitHub (Apr 10, 2025).
Check Existing Issues
Problem Description
Currently the communication to Qdrant relies on HTTP. You can get higher throughput by using gRPC with Qdrant.
Desired Solution you'd like
This is already supported by the Library used by OpenWebUI. It requires a boolean field and a port.
See here: https://github.com/qdrant/qdrant-client?tab=readme-ov-file#grpc
Related code: https://github.com/open-webui/open-webui/blob/dev/backend/open_webui/retrieval/vector/dbs/qdrant.py#L24
Alternatives Considered
None
Additional Context
No response
@gaby commented on GitHub (Apr 10, 2025):
How many config options should be added for this?
Do those make sense?