Repository navigation
Configuration: Minimize API calls #82
Description
Describe the bug
In the Configuration > Library module, multiple unnecessary API calls are being triggered. The system first fetches a batch of versions and then makes additional API calls for each individual version. This results in a large number of requests (N+1 issue), which can impact performance and potentially overload the backend when multiple users access the page simultaneously.
To Reproduce
Steps to reproduce the behavior:
- Go to Configuration > Library page
- Open the browser Network tab
- Observe the API call:
/api/configs/{config_id}/versions
- Then observe multiple follow-up calls:
/api/configs/{config_id}/versions/{version_number}
- Notice that multiple API requests are triggered for each version
- Repeat with different version multiple configurations → number of API calls increases significantly
Expected behavior
The system should minimise API calls by:
- To get the data like batch wise like first we need to show 5-10 version then fetch the next config version when the user clicks on the
Load morebutton or etc. then will be bit optimized structure. - Avoiding multiple per-version API calls.
Screenshots
Metadata
Metadata
Assignees
Type
Projects
- Status
Activity
[-]Performance Issue: Excessive API Calls in Configuration > Library Module[/-][+]Configuration: Minimize API calls[/+]Ayush8923 commentedon Mar 21, 2026
Also, there are a few more places where multiple API calls are being triggered. We should review these flows as well and try to minimize unnecessary requests.
Evaluation Page
On the Evaluation page (check the Network tab), multiple API calls are triggered to fetch versions and their corresponding IDs. This data is primarily used in the Configuration dropdown. We should review this flow and explore if there’s a way to reduce the number of API calls.
Version Comparison Flow
In the flow:
Currently, data for all versions is fetched upfront. Ideally, we should fetch data only for the selected versions when the user initiates a comparison, instead of loading all version data initially.
Additionally, we should ensure that each page only fetches the data it actually needs. This will help avoid unnecessary backend load and improve overall performance.
Ayush8923 commentedon Mar 27, 2026
This has been completed. Closing this issue.
PR reference: #83