Skip to content

⚡ Bolt: 불필요한 방어적 Set 복사 제거로 성능 개선 - #402

Closed
seonghobae wants to merge 1 commit into
mainfrom
bolt-set-optimization-10666547897989591516
Closed

⚡ Bolt: 불필요한 방어적 Set 복사 제거로 성능 개선#402
seonghobae wants to merge 1 commit into
mainfrom
bolt-set-optimization-10666547897989591516

Conversation

@seonghobae

@seonghobae seonghobae commented Aug 12, 2026

Copy link
Copy Markdown
Contributor

💡 What: transcript_search.py에서 검색어 처리 루프 내부의 초기 Set 할당 시, 불필요한 방어적 복사(set(postings))를 제거하고 참조로 대체했습니다.
🎯 Why: Python의 & 연산자는 본질적으로 새로운 Set을 반환하기 때문에, 교집합 연산을 수행할 때 초기 소스 Set을 O(N) 비용을 들여 복사할 필요가 없습니다. 이 불필요한 복사는 중복된 메모리 할당 및 성능 저하를 초래합니다.
📊 Impact: 초기 복사 오버헤드를 제거하여 다중 키워드 검색 시의 메모리 할당을 방지하고 실행 속도를 개선했습니다.
🔬 Measurement: 테스트 통과 여부 및 검색 쿼리 벤치마크를 통해 성능 향상을 확인할 수 있습니다.


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

Summary by CodeRabbit

  • 성능 개선
    • 여러 검색어를 함께 검색할 때 불필요한 데이터 복사를 줄여 검색 처리가 더 효율적으로 수행되도록 개선했습니다.

`transcript_search.py`에서 검색어 처리 루프 내부의 초기 Set 할당 시, 불필요한 방어적 복사(`set(postings)`)를 제거하고 참조로 대체했습니다.
Python의 `&` 연산자는 본질적으로 새로운 Set을 반환하기 때문에, 교집합 연산을 수행할 때 초기 소스 Set을 복사할 필요가 없어 메모리 할당 및 실행 시간을 절약합니다.
@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.

@coderabbitai

coderabbitai Bot commented Aug 12, 2026

Copy link
Copy Markdown

Review Change Stack

No actionable comments were generated in the recent review. 🎉

ℹ️ Recent review info
⚙️ Run configuration

Configuration used: Organization UI

Review profile: CHILL

Plan: Pro Plus

Run ID: 43de9ab2-262b-4daf-ac78-3da469c79717

📥 Commits

Reviewing files that changed from the base of the PR and between a8e4956 and 8410681.

📒 Files selected for processing (2)
  • .jules/bolt.md
  • transcript_search.py

📝 Walkthrough

Walkthrough

TranscriptIndex.search가 첫 번째 검색어의 postings 집합을 복사하지 않고 직접 사용합니다. 후속 검색어의 교집합 계산은 유지됩니다. 관련 최적화 지침도 .jules/bolt.md에 추가되었습니다.

Changes

검색 교집합 최적화

Layer / File(s) Summary
첫 번째 postings 집합 직접 사용
transcript_search.py, .jules/bolt.md
TranscriptIndex.search가 첫 번째 postings 집합을 직접 참조합니다. 후속 검색어부터는 기존과 같이 교집합을 계산합니다. 해당 최적화 지침을 문서에 기록했습니다.

Estimated code review effort: 1 (Trivial) | ~5 minutes

Possibly related PRs

🚥 Pre-merge checks | ✅ 5
✅ Passed checks (5 passed)
Check name Status Explanation
Description Check ✅ Passed Check skipped - CodeRabbit’s high-level summary is enabled.
Title check ✅ Passed 제목은 불필요한 Set 복사 제거와 성능 개선이라는 변경의 핵심을 정확하고 간결하게 설명합니다.
Docstring Coverage ✅ Passed No functions found in the changed files to evaluate docstring coverage. Skipping docstring coverage check.
Linked Issues check ✅ Passed Check skipped because no linked issues were found for this pull request.
Out of Scope Changes check ✅ Passed Check skipped because no linked issues were found for this pull request.
✨ Finishing Touches
📝 Generate docstrings
  • Create stacked PR
  • Commit on current branch
🧪 Generate unit tests (beta)
  • Create PR with unit tests
  • Commit unit tests in branch bolt-set-optimization-10666547897989591516

Thanks for using CodeRabbit! It's free for OSS, and your support helps us grow. If you like it, consider giving us a shout-out.

❤️ Share

Comment @coderabbitai help to get the list of available commands.

@opencode-agent opencode-agent Bot left a comment

Copy link
Copy Markdown
Contributor

Choose a reason for hiding this comment

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

Pull request overview

OpenCode cannot approve yet because required coverage evidence did not pass.

Review outcome

1. HIGH .github/workflows/opencode-review.yml:1 - Coverage evidence did not prove required test/docstring evidence

  • Problem: The required coverage-evidence job result was failure, so OpenCode cannot establish approval sufficiency for this head.

  • Root cause: Automated approval is only valid when the same-head coverage-evidence job proves supported repository test suites passed and configured docstring gates passed or were advisory, or reports not applicable because no supported source files or package manifests exist. Missing, failed, skipped, unavailable, or unsupported-tooling test evidence is a blocker.

  • Fix: Install or configure the repository test/docstring evidence tooling when source files or package manifests exist, rerun the current-head coverage-evidence job, and approve only after it reports success with required evidence or explicit no-source not-applicable evidence.

  • Regression test: Keep the approval branch checking needs.coverage-evidence.result == success before posting APPROVE, and publish REQUEST_CHANGES when coverage-evidence blocker states such as cancelled, skipped, failed, unsupported-tooling, or below-100 evidence are present.

  • Result: REQUEST_CHANGES

  • Reason: coverage-evidence result was failure, so required test/docstring evidence was not proven for current head 841068155816c1153d2c26a1131eea0f74d39081.

  • Head SHA: 841068155816c1153d2c26a1131eea0f74d39081

  • Workflow run: 31626550257

  • Workflow attempt: 1

Coverage evidence

Coverage evidence job did not run or did not publish coverage evidence.

Changed-File Evidence Map

flowchart LR
  PR["PR changed files"] --> Evidence["OpenCode bounded evidence"]
  Evidence --> S1["Changed file (2 files)"]
  S1 --> I1["repository behavior"]
  I1 --> R1["Review risk: Changed file (2 files)"]
  R1 --> V1["required checks"]
Loading

@opencode-agent

Copy link
Copy Markdown
Contributor

OpenCode Review Overview

  • Head SHA: 841068155816c1153d2c26a1131eea0f74d39081
  • Workflow run: 31626550257
  • Workflow attempt: 1
  • Gate result: REQUEST_CHANGES (approval step)

Pull request overview

OpenCode cannot approve yet because required coverage evidence did not pass.

Review outcome

1. HIGH .github/workflows/opencode-review.yml:1 - Coverage evidence did not prove required test/docstring evidence

  • Problem: The required coverage-evidence job result was failure, so OpenCode cannot establish approval sufficiency for this head.

  • Root cause: Automated approval is only valid when the same-head coverage-evidence job proves supported repository test suites passed and configured docstring gates passed or were advisory, or reports not applicable because no supported source files or package manifests exist. Missing, failed, skipped, unavailable, or unsupported-tooling test evidence is a blocker.

  • Fix: Install or configure the repository test/docstring evidence tooling when source files or package manifests exist, rerun the current-head coverage-evidence job, and approve only after it reports success with required evidence or explicit no-source not-applicable evidence.

  • Regression test: Keep the approval branch checking needs.coverage-evidence.result == success before posting APPROVE, and publish REQUEST_CHANGES when coverage-evidence blocker states such as cancelled, skipped, failed, unsupported-tooling, or below-100 evidence are present.

  • Result: REQUEST_CHANGES

  • Reason: coverage-evidence result was failure, so required test/docstring evidence was not proven for current head 841068155816c1153d2c26a1131eea0f74d39081.

  • Head SHA: 841068155816c1153d2c26a1131eea0f74d39081

  • Workflow run: 31626550257

  • Workflow attempt: 1

Coverage evidence

Coverage evidence job did not run or did not publish coverage evidence.

Changed-File Evidence Map

flowchart LR
  PR["PR changed files"] --> Evidence["OpenCode bounded evidence"]
  Evidence --> S1["Changed file (2 files)"]
  S1 --> I1["repository behavior"]
  I1 --> R1["Review risk: Changed file (2 files)"]
  R1 --> V1["required checks"]
Loading

Copy link
Copy Markdown
Contributor Author

Closing as an exact functional duplicate of #389. Exact patch comparison shows the same sole production change in TranscriptIndex.search: use the first postings set by reference, then rely on non-mutating & intersections. #389 is already based on the live main tip; the documentation variants here add no unique runtime or acceptance behavior.

@seonghobae seonghobae closed this Aug 14, 2026
@google-labs-jules

Copy link
Copy Markdown

Closing as an exact functional duplicate of #389. Exact patch comparison shows the same sole production change in TranscriptIndex.search: use the first postings set by reference, then rely on non-mutating & intersections. #389 is already based on the live main tip; the documentation variants here add no unique runtime or acceptance behavior.

Understood. Acknowledging that this work is an exact functional duplicate of #389 and stopping work on this task.

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