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
In summary, this PR's purpose is to move the leaderboard computation to the backend to separate rendering logic and computation and allow for further optimizations.
Added
Created backend/utils/leaderboard.py to hold the backend logic for computing the leaderboard, including the model ranking, elo calculation, cosine similarity, and getting the embedding model and tokenizer.
Changed
Modified lib/components/admin/Evaluation/Leaderboard.svelte to move existing computation and loading to the backend and fetch the leaderboard by calling a helper function called getLeaderboard passing the current query, token, and current value of the $models svelte store. Couldnt fetch the models from the backend for some reason so just using this existing store.
Modified lib/apis/evaluations/index.ts to add the getLeaderboard helper function which makes a post request to the /evaluations/leaderboard endpoint with the models array.
Modified backend/open_webui/routers/evaluations,py to create this endpoint for /leaderboard which receives the post body from the frontend and uses these models to compute the leaderboard (from openwebui.utils.leaderboard mentioned above.)
Additional Information
Let me know what needs to be changed to iterate on this
Contributor License Agreement
By submitting this pull request, I confirm that I have read and fully agree to the Contributor License Agreement (CLA), 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/15392
**Author:** [@ayanahye](https://github.com/ayanahye)
**Created:** 6/29/2025
**Status:** ❌ Closed
**Base:** `dev` ← **Head:** `perf-move-eval-comp-backend`
---
### 📝 Commits (1)
- [`5dbdee1`](https://github.com/open-webui/open-webui/commit/5dbdee17152e4c235b6cdc7d05514fa5b5d4889f) perf move leaderboard computation to backend
### 📊 Changes
**4 files changed** (+191 additions, -253 deletions)
<details>
<summary>View changed files</summary>
📝 `backend/open_webui/routers/evaluations.py` (+14 -0)
➕ `backend/open_webui/utils/leaderboard.py` (+118 -0)
📝 `src/lib/apis/evaluations/index.ts` (+35 -0)
📝 `src/lib/components/admin/Evaluations/Leaderboard.svelte` (+24 -253)
</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
- In summary, this PR's purpose is to move the leaderboard computation to the backend to separate rendering logic and computation and allow for further optimizations.
### Added
- Created `backend/utils/leaderboard.py` to hold the backend logic for computing the leaderboard, including the model ranking, elo calculation, cosine similarity, and getting the embedding model and tokenizer.
### Changed
- Modified `lib/components/admin/Evaluation/Leaderboard.svelte` to move existing computation and loading to the backend and fetch the leaderboard by calling a helper function called `getLeaderboard` passing the current query, token, and current value of the $models svelte store. Couldnt fetch the models from the backend for some reason so just using this existing store.
- Modified `lib/apis/evaluations/index.ts` to add the getLeaderboard helper function which makes a post request to the `/evaluations/leaderboard` endpoint with the models array.
- Modified `backend/open_webui/routers/evaluations,py` to create this endpoint for `/leaderboard` which receives the post body from the frontend and uses these models to compute the leaderboard (from `openwebui.utils.leaderboard` mentioned above.)
---
### Additional Information
- Let me know what needs to be changed to iterate on this
### Contributor License Agreement
By submitting this pull request, I confirm that I have read and fully agree to the [Contributor License Agreement (CLA)](/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>
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.
📋 Pull Request Information
Original PR: https://github.com/open-webui/open-webui/pull/15392
Author: @ayanahye
Created: 6/29/2025
Status: ❌ Closed
Base:
dev← Head:perf-move-eval-comp-backend📝 Commits (1)
5dbdee1perf move leaderboard computation to backend📊 Changes
4 files changed (+191 additions, -253 deletions)
View changed files
📝
backend/open_webui/routers/evaluations.py(+14 -0)➕
backend/open_webui/utils/leaderboard.py(+118 -0)📝
src/lib/apis/evaluations/index.ts(+35 -0)📝
src/lib/components/admin/Evaluations/Leaderboard.svelte(+24 -253)📄 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:
devbranch.Changelog Entry
Description
Added
backend/utils/leaderboard.pyto hold the backend logic for computing the leaderboard, including the model ranking, elo calculation, cosine similarity, and getting the embedding model and tokenizer.Changed
lib/components/admin/Evaluation/Leaderboard.svelteto move existing computation and loading to the backend and fetch the leaderboard by calling a helper function calledgetLeaderboardpassing the current query, token, and current value of the $models svelte store. Couldnt fetch the models from the backend for some reason so just using this existing store.lib/apis/evaluations/index.tsto add the getLeaderboard helper function which makes a post request to the/evaluations/leaderboardendpoint with the models array.backend/open_webui/routers/evaluations,pyto create this endpoint for/leaderboardwhich receives the post body from the frontend and uses these models to compute the leaderboard (fromopenwebui.utils.leaderboardmentioned above.)Additional Information
Contributor License Agreement
By submitting this pull request, I confirm that I have read and fully agree to the Contributor License Agreement (CLA), 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.