Repository navigation
perf(search): search up to eight live accounts at once - #8891
Conversation
|
The latest updates on your projects. Learn more about Vercel for GitHub. |
![cubic-dev-ai[bot]](https://avatars.githubusercontent.com/in/1082092?s=60&v=4){kind=small}
There was a problem hiding this comment.
No issues found across 1 file
Confidence score: 5/5
- Automated review surfaced no issues in the provided summaries.
- No files require special attention.
Heads up: you’ve reached your flex budget. Increase your flex budget or wait for usage to reset.
Turn on auto-fix | Re-trigger cubic
 |
A live search waits for every account before fusing results, and accounts ran four at a time, so an organization with five to eight connected accounts paid a second full provider round trip on every unscoped search. Production seven-account searches took about 2.1 s at p50 against about 0.6 s for one account. Each account is a single provider call, so eight at once stays well inside provider and token-refresh limits.
327e6b7 to
0ad0911
Compare
|
@cubic-dev-ai review this PR |
@waleedlatif1 I have started the AI code review. It will take a few minutes to complete. |
There was a problem hiding this comment.
No issues found across 1 file
Confidence score: 5/5
- Automated review surfaced no issues in the provided summaries.
- No files require special attention.
Heads up: you’ve reached your flex budget. Increase your flex budget or wait for usage to reset.
Turn on auto-fix | Re-trigger cubic
This branch was previously deployed
1 participant
Summary
searchLiveKnowledgewaits for every selected account before fusing results, and it searched accounts four at a time (ACCOUNT_CONCURRENCY). An organization with 5–8 connected accounts paid a second full provider round trip on every unscoped search.MAX_ACCOUNTS(20) still bounds the total.Test plan
🤖 Generated with Claude Code