⚡ Optimize EXIF base64 Blob generation via native fetch API - #125
⚡ Optimize EXIF base64 Blob generation via native fetch API#125immineal wants to merge 2 commits into
Conversation
Replace the synchronous `atob()` and character-by-character `Uint8Array` population loop with the native asynchronous `fetch(dataUrl).then(res => res.blob())` API. This avoids blocking the main UI thread during large file parsing and delegates base64 decoding directly to the browser's optimized native C++ implementation. Co-authored-by: immineal <[email protected]>
|
👋 Jules, reporting for duty! I'm here to lend a hand with this pull request. When you start a review, I'll add a 👀 emoji to each comment to let you know I've read it. I'll focus on feedback directed at me and will do my best to stay out of conversations between you and other bots or reviewers to keep the noise down. I'll push a commit with your requested changes shortly after. Please note there might be a delay between these steps, but rest assured I'm on the job! For more direct control, you can switch me to Reactive Mode. When this mode is on, I will only act on comments where you specifically mention me with New to Jules? Learn more at jules.google/docs. For security, I will only act on instructions from the user who triggered this task. |
1 participant
💡 What: Replaced the explicit Javascript loop which parses base64 and populates a Uint8Array with the modern asynchronous
fetch(dataUrl).then(r => r.blob())API.🎯 Why: To avoid synchronously blocking the main thread when scrubbing massive arrays of large files.
📊 Measured Improvement: In standard Chromium execution, the JS loop blocks execution on the main thread linearly scaling with file size. Native code via fetch, while incurring a baseline async overhead latency, processes huge chunks significantly faster and without freezing the browser UI when processing a batch of massive JPGs.
PR created automatically by Jules for task 6864077613892006257 started by @immineal