⚡ Bolt: [performance improvement] optimize sequence number queries for job events - #146
⚡ Bolt: [performance improvement] optimize sequence number queries for job events#146crabcanon wants to merge 1 commit into
Conversation
Replaced memory-heavy query (`list_for_job(limit=1000)[-1]`) with an efficient SQL scalar aggregation query `get_max_sequence_no` for computing the next sequence number in JobControlServices. Co-authored-by: crabcanon <3458947+crabcanon@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.
|
1 participant
💡 What:
Replaced
list_for_job(limit=1000)[-1]which loaded up to 1000 entireJobEventrows into Python memory with a fastget_max_sequence_nodatabase-side aggregation method usingfunc.coalesce(func.max(...), 0).🎯 Why:
Fetching list objects to calculate the max sequence causes high database transfer, memory bloat, and slower processing during large event insertions. By performing the maximum calculation natively via SQL, we resolve an effective N+1 style bottleneck.
📊 Impact:
Significantly reduces query serialization/deserialization time and memory footprint during
JobControlServicesequence calculations, resulting in much faster job event logging capabilities.🔬 Measurement:
Tested and verified with the integration test suite and code review, passing successfully with no semantic behaviour change.
PR created automatically by Jules for task 5502269953196930861 started by @crabcanon