Skip to content

⚡ Bolt: [performance improvement] Hoist static strings and expensive SHA-256 out of loop#256

Open
seonghobae wants to merge 1 commit into
masterfrom
jules-11568844940393443262-f6819a97
Open

⚡ Bolt: [performance improvement] Hoist static strings and expensive SHA-256 out of loop#256
seonghobae wants to merge 1 commit into
masterfrom
jules-11568844940393443262-f6819a97

Conversation

@seonghobae

Copy link
Copy Markdown
Collaborator

💡 What:
process_dir 내부에 위치하던 불변 정적 문자열(cssContent, css)과 비용이 큰 SHA-256 해시 연산 코드를 최상위 레벨의 private val 상수로 호이스팅했습니다.

🎯 Why:
해당 변수들은 파일 디렉토리 크롤링 시 process_dir 호출마다 변하지 않는 고정된 값입니다. 그럼에도 불구하고 매번 호출될 때마다 무거운 SHA-256 연산과 대량의 문자열 할당이 반복적으로 발생하여 불필요한 메모리(GC) 및 CPU 오버헤드를 유발하고 있었습니다.

📊 Impact:
디렉토리를 순회할 때마다 발생하던 중복된 메모리 할당 및 해시 연산 비용이 사라졌습니다. 특히 많은 디렉토리(1,000개 이상)를 순회할 때 처리 속도가 개선되며 메모리 압박이 대폭 줄어듭니다.

🔬 Measurement:
테스트 커버리지 100%를 유지하는지 확인하기 위해 ./gradlew clean test jacocoTestReport jacocoTestCoverageVerification --continue를 실행하여 통과함을 확인했습니다.


PR created automatically by Jules for task 11568844940393443262 started by @seonghobae

…SHA-256 out of loop

💡 What:
`process_dir` 내부에 위치하던 불변 정적 문자열(`cssContent`, `css`)과 비용이 큰 SHA-256 해시 연산 코드를 최상위 레벨의 `private val` 상수로 호이스팅했습니다.

🎯 Why:
해당 변수들은 파일 디렉토리 크롤링 시 `process_dir` 호출마다 변하지 않는 고정된 값입니다. 그럼에도 불구하고 매번 호출될 때마다 무거운 SHA-256 연산과 대량의 문자열 할당이 반복적으로 발생하여 불필요한 메모리(GC) 및 CPU 오버헤드를 유발하고 있었습니다.

📊 Impact:
디렉토리를 순회할 때마다 발생하던 중복된 메모리 할당 및 해시 연산 비용이 사라졌습니다. 특히 많은 디렉토리(1,000개 이상)를 순회할 때 처리 속도가 개선되며 메모리 압박이 대폭 줄어듭니다.

🔬 Measurement:
테스트 커버리지 100%를 유지하는지 확인하기 위해 `./gradlew clean test jacocoTestReport jacocoTestCoverageVerification --continue`를 실행하여 통과함을 확인했습니다.
Copilot AI review requested due to automatic review settings July 24, 2026 03:38
@google-labs-jules

Copy link
Copy Markdown

👋 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.

Copilot AI left a comment

Copy link
Copy Markdown

Choose a reason for hiding this comment

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

Pull request overview

This PR improves html4tree’s directory indexing performance by hoisting per-directory invariant CSS strings and the SHA-256 CSP hash computation out of process_dir into top-level private vals, reducing repeated allocations and hashing work during large crawls.

Changes:

  • Hoisted cssContent, css, and styleHash from inside process_dir to top-level private vals to avoid repeated string allocation and SHA-256 hashing per directory.
  • Added a new Bolt learning entry documenting the optimization rationale and intended impact.

Reviewed changes

Copilot reviewed 2 out of 2 changed files in this pull request and generated 1 comment.

File Description
src/main/kotlin/html4tree/main.kt Hoists static CSS and CSP hash computation out of process_dir to reduce repeated work during directory traversal.
.jules/bolt.md Documents the performance optimization as a new Bolt learning/action entry.

💡 Add Copilot custom instructions for smarter, more guided reviews. Learn how to get started.

Comment on lines +313 to 316
private val css = """
<style>
${cssContent} </style>
"""
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.

2 participants