⚡ Bolt: Cache compiled context lexicon regexes - #38
Conversation
This adds memoization to `_compiled_context_lexicon` using `@functools.lru_cache`, which saves substantial overhead from continuously recompiling large sets of regexes for every span assertion. Co-authored-by: zrt219 <199104500+zrt219@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.
|
💡 What: Added
@functools.lru_cache(maxsize=16)to the_compiled_context_lexiconfunction.🎯 Why: To prevent the repeated, expensive compilation of regular expressions used for clinical span assertions (temporality, uncertainty, negation).
📊 Impact: The benchmarking of 1000 iterations for
resolve_temporalityshowed an execution time drop from ~0.87 seconds to ~0.02 seconds, dramatically reducing CPU overhead and speeding up high-throughput text processing.🔬 Measurement: Verify the improvement by running a benchmarking script calling
resolve_temporality(or any function relying on_compiled_context_lexicon) repeatedly and observing the execution times.PR created automatically by Jules for task 15373112135257817424 started by @zrt219