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
I’m encountering a significant performance issue on the Assistant page. It seems that the API is querying all available data in one go with each request, often resulting in the retrieval of tens of megabytes of content at once. This is causing severe lag in the browser, to the point where the page becomes almost unusable.
Expected behavior
I suggest implementing proper pagination and lazy loading, so that data is fetched in smaller chunks as needed, rather than retrieving everything at once. This would greatly enhance the page's performance and responsiveness.
Steps to reproduce
1. Add several hundred assistants to the system, even if the conversation data for each assistant is minimal.
2. Switch to the Assistant page.
Additional information
No response
The text was updated successfully, but these errors were encountered:
KevinHuSh
changed the title
[Bug]: Excessive Data Loading in Assistant Page Causing Severe Lag
[Feature Request]: Pagination for list of assistants. Excessive Data Loading in Assistant Page Causing Severe Lag
Jan 3, 2025
Is there an existing issue for the same bug?
RAGFlow workspace code commit ID
none
RAGFlow image version
v0.15.1 full
Other environment information
No response
Actual behavior
I’m encountering a significant performance issue on the Assistant page. It seems that the API is querying all available data in one go with each request, often resulting in the retrieval of tens of megabytes of content at once. This is causing severe lag in the browser, to the point where the page becomes almost unusable.
Expected behavior
I suggest implementing proper pagination and lazy loading, so that data is fetched in smaller chunks as needed, rather than retrieving everything at once. This would greatly enhance the page's performance and responsiveness.
Steps to reproduce
Additional information
No response
The text was updated successfully, but these errors were encountered: