Release query results before they become a timeout

A query can finish while its unread response still holds the connection.

Prompt

Evaluate and apply this CI technique to my repository: Release query results before they become a timeout.

A query can finish while its unread response still holds the connection.

Read the technique and its source-backed company examples: https://starsling.dev/ci-playbooks/techniques/release-query-results.md

Inspect this repository’s CI workflows, build and test commands, dependencies, and recent run timings. Identify where this technique applies and explain the expected benefit using this repository’s evidence.
Measure a baseline from recent comparable runs: elapsed time, queue time, runner minutes and failures where available. If data is unavailable, say what cannot be measured.
Compare relevant company approaches, checking prerequisites, platform differences and tradeoffs. Rank applicable options by evidence, fit and measurable opportunity; do not present company results as predictions for this repo.
Recommend the smallest safe change, show what checks and fallback paths remain, and ASK ME WHICH CHANGE TO APPROVE BEFORE EDITING ANY FILES.
Only after approval, work on a new feature branch, make one reversible change, and open a reviewable pull request. Never merge or push to a default or protected branch.
Keep required checks, test coverage, deployment and release behavior intact. Validate the change and compare equivalent runs where possible; report limitations and what should be monitored after merge.

View all playbooks

How Mastra used this technique

Read what Mastra changed and follow the original sources.

Release query results before they become a timeout

StarSling’s agent added result consumption to two ClickHouse initialization queries in Mastra, so each query releases its connection as soon as its result is read.

The PR reports five same-commit trials per arm: job median 530s to 298s, about 44% less elapsed time. Source

Use it when: An integration step spends most of its time waiting after a query has already completed.
Before applying it: Keep query behavior and result validation. Profile connection lifetimes first.

How Mastra used this technique

Release query results before they become a timeout

Related techniques

Build before starting the emulator

Install a pinned tool release

Reuse exact baseline analysis results

Company Playbooks