⚡ Bolt: [SQLite 연결 성능 최적화]

[seonghobae]

💡 What

job_store.py의 JobStore 클래스에서 데이터베이스 연결 시마다 실행되던 PRAGMA journal_mode=WAL을 데이터베이스 초기화 시 한 번만 실행되도록 변경했습니다.

🎯 Why

SQLite의 WAL(Write-Ahead Logging) 모드 설정은 데이터베이스 파일 수준에서 유지됩니다. 짧은 주기로 수많은 연결을 생성하고 해제하는 현재 아키텍처에서, 매번 연결마다 WAL 모드를 재설정하는 것은 불필요한 오버헤드를 발생시킵니다.

📊 Impact

연결 획득 시의 오버헤드가 감소하여, 비동기 작업 폴링 등 빈번한 데이터베이스 접근이 일어나는 시나리오에서 전체적인 시스템 성능과 응답성이 향상됩니다. 벤치마크 결과 데이터베이스 연결당 성능이 크게 개선되었습니다.

🔬 Measurement

단위 테스트 스위트가 여전히 통과하며, coverage 100%가 유지됨을 확인했습니다.

---

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

[google-labs-jules]

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

Warning

Review limit reached

@seonghobae, you've reached your PR review limit, so we couldn't start this review.

Next review available in: 11 minutes

Enable usage-based reviews in Billing to review now. Otherwise, wait until the next included review is available.
You're only billed for reviews past your plan's rate limits ($0.25/file).

How can I continue?

After more reviews become available, a review can be triggered using the @coderabbitai review command as a PR comment. Alternatively, push new commits to this PR.

To avoid repeated limits, reduce automatic review volume by pausing incremental auto-reviews earlier, using label-based review opt-in, excluding WIP or generated PR titles, or requesting reviews manually when the PR is ready. If your team needs uninterrupted high-volume reviews, an organization admin can enable usage-based reviews.

How do review limits work?

CodeRabbit enforces per-developer PR review limits for each organization. Most developers receive the normal plan review availability.

For paid Pro and Pro+ PR reviews, CodeRabbit uses adaptive limits for sustained high-volume activity. When a developer's recent PR review activity reaches the 95th percentile or higher among CodeRabbit users, additional reviews become available more gradually as earlier reviews age out of the rolling window.

Please refer docs for additional details.

Review details

⚙️ Run configuration

Configuration used: Organization UI

Review profile: CHILL

Plan: Pro Plus

Run ID: 6414fde9-e4a8-4cea-853c-d0c0c4b84d9a

📥 Commits

Reviewing files that changed from the base of the PR and between 5a92586 and 315af8d.

📒 Files selected for processing (3)

• .jules/bolt.md
• CHANGELOG.md
• job_store.py

---

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