Skip to content

⚡ Bolt: Optimize keyword density parsing by hoisting constants#280

Open
anchapin wants to merge 1 commit intomainfrom
bolt/optimize-keyword-density-3605191710944001867
Open

⚡ Bolt: Optimize keyword density parsing by hoisting constants#280
anchapin wants to merge 1 commit intomainfrom
bolt/optimize-keyword-density-3605191710944001867

Conversation

@anchapin
Copy link
Copy Markdown
Owner

@anchapin anchapin commented May 2, 2026

💡 What: Hoisted static variables (regex patterns, common fallback keywords, and tech keywords) in cli/utils/keyword_density.py to module-level constants. Converted the tech keywords list to a set.

🎯 Why: To reduce the CPU overhead caused by repeated compilation of regular expressions and to eliminate the memory overhead associated with dynamically re-allocating static lists inside frequently called functions during the keyword density analysis. Using a set for the tech keywords drops lookup complexity from O(n) to O(1).

📊 Impact: Lowers memory pressure and execution time for the keyword density tool. Specifically useful when parsing large, dense job descriptions against several pattern variants, preventing repeated setup operations.

🔬 Measurement: Ensure all tests across tests/test_keyword_density.py pass and execution completes without performance regressions in standard use. Run python -m pytest tests/ to confirm.


PR created automatically by Jules for task 3605191710944001867 started by @anchapin

- Moved title and company regex patterns to module-level constants `_TITLE_PATTERNS` and `_COMPANY_PATTERNS` to avoid repeated re-compilation.
- Extracted static fallback tech keywords into a module-level set (`_TECH_KEYWORDS`) to optimize membership checking to O(1) time complexity and eliminate redundant allocations.
- Moved `common_keywords` from inside `_simple_keyword_extraction` to a module-level constant list `_COMMON_KEYWORDS`.

Co-authored-by: anchapin <[email protected]>
@google-labs-jules
Copy link
Copy Markdown
Contributor

👋 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 @jules. You can find this option in the Pull Request section of your global Jules UI settings. You can always switch back!

New to Jules? Learn more at jules.google/docs.


For security, I will only act on instructions from the user who triggered this task.

Copy link
Copy Markdown

@sourcery-ai sourcery-ai Bot left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Sorry @anchapin, you have reached your weekly rate limit of 500000 diff characters.

Please try again later or upgrade to continue using Sourcery

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant