[PR #13165] [MERGED] perf: all knowledge searches in parallel in non-hybrid mode #9915

New Issue

GiteaMirror · 2025-11-11T18:34:47-06:00

GiteaMirror commented

2025-11-11 18:34:47 -06:00

📋 Pull Request Information

Original PR: https://github.com/open-webui/open-webui/pull/13165
Author: @almajo
Created: 4/23/2025
Status: ✅ Merged
Merged: 4/23/2025
Merged by: @tjbck

Base: dev ← Head: perf/parallel_knowledge_search

📝 Commits (1)

d182155 ~ call knowledge searches in parallel in non-hybrid mode

📊 Changes

1 file changed (+40 additions, -16 deletions)

View changed files

📝 backend/open_webui/retrieval/utils.py (+40 -16)

📄 Description

Pull Request Checklist

Note to first-time contributors: Please open a discussion post in Discussions and describe your changes before submitting a pull request.

Before submitting, make sure you've checked the following:

Target branch: Please verify that the pull request targets the dev branch.
Description: Provide a concise description of the changes made in this pull request.
Changelog: Ensure a changelog entry following the format of Keep a Changelog is added at the bottom of the PR description.
Documentation: Have you updated relevant documentation Open WebUI Docs, or other documentation sources?
Dependencies: Are there any new dependencies? Have you updated the dependency versions in the documentation?
Testing: Have you written and run sufficient tests to validate the changes?
Code review: Have you performed a self-review of your code, addressing any coding standard issues and ensuring adherence to the project's coding standards?
Prefix: To clearly categorize this pull request, prefix the pull request title using one of the following:
- BREAKING CHANGE: Significant changes that may affect compatibility
- build: Changes that affect the build system or external dependencies
- ci: Changes to our continuous integration processes or workflows
- chore: Refactor, cleanup, or other non-functional code changes
- docs: Documentation update or addition
- feat: Introduces a new feature or enhancement to the codebase
- fix: Bug fix or error correction
- i18n: Internationalization or localization changes
- perf: Performance improvement
- refactor: Code restructuring for better maintainability, readability, or scalability
- style: Changes that do not affect the meaning of the code (white space, formatting, missing semi-colons, etc.)
- test: Adding missing tests or correcting existing tests
- WIP: Work in progress, a temporary label for incomplete or ongoing work

Changelog Entry

Description

Currently each query (up to 3 are generated for each user query) and collection (one model can have access to many knowledge bases) is queried sequentially, leading to a large waiting time while most of the time is spent waiting for IO. For hybrid search, the same functionality is already implemented.

Similar to query_collection_with_hybrid_search, we want to leverage multi-threading in order to speed up rag performance without hybrid search by a big factor.

Changed

only make one embedding call with all queries -> less api calls
each (query, collection) pair is queried in a separate thread

Contributor License Agreement

By submitting this pull request, I confirm that I have read and fully agree to the CONTRIBUTOR_LICENSE_AGREEMENT, and I am providing my contributions under its terms.

_{🔄 This issue represents a GitHub Pull Request. It cannot be merged through Gitea due to API limitations.}

## 📋 Pull Request Information **Original PR:** https://github.com/open-webui/open-webui/pull/13165 **Author:** [@almajo](https://github.com/almajo) **Created:** 4/23/2025 **Status:** ✅ Merged **Merged:** 4/23/2025 **Merged by:** [@tjbck](https://github.com/tjbck) **Base:** `dev` ← **Head:** `perf/parallel_knowledge_search` --- ### 📝 Commits (1) - [`d182155`](https://github.com/open-webui/open-webui/commit/d182155fac4cce2c0afaebc5117671cb8bbf153d) ~ call knowledge searches in parallel in non-hybrid mode ### 📊 Changes **1 file changed** (+40 additions, -16 deletions) <details> <summary>View changed files</summary> 📝 `backend/open_webui/retrieval/utils.py` (+40 -16) </details> ### 📄 Description # Pull Request Checklist ### Note to first-time contributors: Please open a discussion post in [Discussions](https://github.com/open-webui/open-webui/discussions) and describe your changes before submitting a pull request. **Before submitting, make sure you've checked the following:** - [x] **Target branch:** Please verify that the pull request targets the `dev` branch. - [x] **Description:** Provide a concise description of the changes made in this pull request. - [x] **Changelog:** Ensure a changelog entry following the format of [Keep a Changelog](https://keepachangelog.com/) is added at the bottom of the PR description. - [ ] **Documentation:** Have you updated relevant documentation [Open WebUI Docs](https://github.com/open-webui/docs), or other documentation sources? - [ ] **Dependencies:** Are there any new dependencies? Have you updated the dependency versions in the documentation? - [ ] **Testing:** Have you written and run sufficient tests to validate the changes? - [x] **Code review:** Have you performed a self-review of your code, addressing any coding standard issues and ensuring adherence to the project's coding standards? - [x] **Prefix:** To clearly categorize this pull request, prefix the pull request title using one of the following: - **BREAKING CHANGE**: Significant changes that may affect compatibility - **build**: Changes that affect the build system or external dependencies - **ci**: Changes to our continuous integration processes or workflows - **chore**: Refactor, cleanup, or other non-functional code changes - **docs**: Documentation update or addition - **feat**: Introduces a new feature or enhancement to the codebase - **fix**: Bug fix or error correction - **i18n**: Internationalization or localization changes - **perf**: Performance improvement - **refactor**: Code restructuring for better maintainability, readability, or scalability - **style**: Changes that do not affect the meaning of the code (white space, formatting, missing semi-colons, etc.) - **test**: Adding missing tests or correcting existing tests - **WIP**: Work in progress, a temporary label for incomplete or ongoing work # Changelog Entry ### Description Currently each query (up to 3 are generated for each user query) and collection (one model can have access to many knowledge bases) is queried sequentially, leading to a large waiting time while most of the time is spent waiting for IO. For hybrid search, the same functionality is already implemented. - Similar to query_collection_with_hybrid_search, we want to leverage multi-threading in order to speed up rag performance without hybrid search by a big factor. ### Changed - only make one embedding call with all queries -> less api calls - each (query, collection) pair is queried in a separate thread ### Contributor License Agreement By submitting this pull request, I confirm that I have read and fully agree to the [CONTRIBUTOR_LICENSE_AGREEMENT](CONTRIBUTOR_LICENSE_AGREEMENT), and I am providing my contributions under its terms. --- <sub>🔄 This issue represents a GitHub Pull Request. It cannot be merged through Gitea due to API limitations.</sub>

GiteaMirror added the pull-request label 2025-11-11 18:34:47 -06:00

GiteaMirror closed this issue

2025-11-11 18:34:48 -06:00

GiteaMirror referenced this issue

2026-04-19 21:51:15 -05:00

[GH-ISSUE #9915] feat: expand the deepseek_r1<think>result instead of automatically collapsing it #15698

GiteaMirror referenced this issue

2026-04-25 05:16:03 -05:00

[GH-ISSUE #9915] feat: expand the deepseek_r1<think>result instead of automatically collapsing it #31226

GiteaMirror referenced this issue

2026-05-05 16:09:34 -05:00

[GH-ISSUE #9915] feat: expand the deepseek_r1<think>result instead of automatically collapsing it #54363