⚡ Bolt: Optimize reading time calculation cache#1037
⚡ Bolt: Optimize reading time calculation cache#1037kuasar-mknd wants to merge 1 commit intomasterfrom
Conversation
|
👋 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. |
💡 What:
Refactored the
getReadingTimefunction insrc/utils/readingTime.tsto use the original text reference as theMapcache key, storing the resulting word count, instead of creating a massive composite string key (${wordsPerMinute}:${text}) that stores the final time.🎯 Why:
The original approach concatenated
wordsPerMinutewith the entire text content (which could be an 800k character blog post) on every single call to construct the cache key. This caused massive unnecessary string allocations and defeated the purpose of caching for large inputs.📊 Measured Improvement:
In a standalone benchmark evaluating a large mock post body (800k characters) 10,000 times:
This prevents large memory spikes during SSG builds or long-running dev server sessions while safely bounding cache size to 1000 items.
PR created automatically by Jules for task 15717022230701921219 started by @kuasar-mknd