⚡ Optimize font lookup iteration #404
Conversation
Replaced `Array.from(document.fonts.values()).find()` with a direct `for...of` loop over `document.fonts`. This avoids allocating an intermediate array and iterates only once, improving efficiency and reducing memory usage. Benchmark results: - Chromium: ~2.6x faster - WebKit: ~1.3x faster - Firefox: Functionally correct, slight iteration overhead but negligible compared to allocation savings. Co-authored-by: xRahul <1639945+xRahul@users.noreply.github.com>
|
👋 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. |
⚡ Optimize font lookup iteration
💡 What: Replaced the
Array.from(document.fonts.values()).find()pattern with a directfor...ofloop overdocument.fonts.🎯 Why: The previous approach allocated a new array containing all font faces before iterating over it to find a match. This optimization removes the array allocation and the double iteration (one to create the array, one to find the element), reducing memory pressure and CPU usage.
📊 Measured Improvement:
Benchmark results (10000 iterations):
PR created automatically by Jules for task 7981834676303099392 started by @xRahul