⚡ Bolt: Optimize KnowledgeGraph search and focus lookups#274
Conversation
Pre-indexed nodes in useMemo to prevent multiple redundant `.toLowerCase()` conversions during keypresses and filtering within the KnowledgeGraph component. Also utilized a Map to switch focus lookup to an O(1) complexity lookup. Co-authored-by: hadsern <5723837+hadsern@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. |
💡 What: Pre-indexed
idandtitlefields insideuseMemoofKnowledgeGraphusing.toLowerCase()onto new fields, alongside adding aMapfor precise object lookup byid. Then refactored the keydown handler and suggestion filtering logic to use these pre-processed properties instead of continuously executing.toLowerCase()calls during string matching.🎯 Why: Repeated string allocations and array traversals triggered by high-frequency inputs like key strokes (
onKeyDown) and suggestion box render updates were creating significant CPU load due to the execution loop redundantly running.toLowerCase()inside every iteraton for each user stroke against a large array of nodes.📊 Impact: Reduces computational overhead significantly by removing$O(N)$ string operations from the main rendering and input loops, converting search loops to use existing lowercased variables and focus resolutions into an $O(1)$ exact Map lookup.
🔬 Measurement: Verifiable by executing the React Profiler in developer tools and observing the render-phase durations and reduced heap allocations when actively typing within the 'Find' inputs inside the Graph page.
PR created automatically by Jules for task 7406408528643236081 started by @hadsern