⚡ Bolt: [performance improvement] Cache domain searches#186
⚡ Bolt: [performance improvement] Cache domain searches#186
Conversation
Added a module-level `Map` cache in `DomainSearch.svelte` to prevent redundant network requests when searching for the same domain multiple times within a 5-minute window. Co-authored-by: yeboster <23556525+yeboster@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. |
|
The latest updates on your projects. Learn more about Vercel for GitHub.
|
1 participant
💡 What: Implemented a client-side cache for domain searches using a Svelte module-scoped
MapinDomainSearch.svelte.🎯 Why: When users type, backspace, or repeatedly check the same domains, the app previously triggered identical, expensive API calls (
$metaNamesSdk.domainRepository.find(domainName)). Caching these results eliminates redundant network requests.📊 Impact: Reduces API calls for repetitive searches by 100% within a 5-minute window (TTL), making the UI feel instantly responsive on cache hits.
🔬 Measurement: Search for "test", wait for the result. Clear the input, type "test" again. The result should appear instantly without a network request.
PR created automatically by Jules for task 17610868626420348148 started by @yeboster