perf(webui): optimize PagedReader for large page counts #2102
Conversation
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
everpcpc
changed the title
everpcpc
changed the title
everpcpc
changed the title
|
The UI is being rewritten, so i am not accepting any PRs on the current webui. |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
2 participants
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Optimize PagedReader Performance for Large Page Counts
Problem
PagedReader becomes very slow with high CPU usage when handling books with 100+ pages.
Changes
Virtual scrolling: Only render 5 carousel items (current page ±2) instead of all pages
Optimized page lookup: Use Map cache instead of nested loops in
toSpreadIndex()Impact