⚡ Optimize EPUB image extraction using ZipFile random access #33
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.
Optimized
ContentRepository.getEpubImageto usejava.util.zip.ZipFileinstead ofZipInputStream.ZipInputStreamrequires scanning the entire stream to find a specific entry, which is O(N) where N is the number of files in the EPUB.ZipFilereads the central directory and allows O(1) (or close to it) access to specific entries.Since
ZipFilerequires a localFileand cannot work onInputStream(e.g., fromcontent://URIs), I implemented a caching mechanism that copies the stream to a temporary local file inepub_cache. This copy happens only once per session/cache lifecycle.Implemented thread-safe file caching using atomic rename (
renameTo) to handle concurrent requests (e.g., multiple images loading from the same EPUB simultaneously). Added robust error handling to clean up corrupted cache files.Performance benchmark demonstrated a 45x improvement (45ms -> 1ms) for a 5000-entry archive.
PR created automatically by Jules for task 16254206562520747317 started by @Aatricks