Skip to content

chore(agents): Expand perf-tuning scope and parallel agent count #1274

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Merged
yamadashy merged 1 commit into from
Mar 21, 2026
Merged

chore(agents): Expand perf-tuning scope and parallel agent count #1274

Changes from all commits
Commits
Show all changes
1 commit
Select commit
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
4 changes: 2 additions & 2 deletions .agents/commands/code/perf-tuning.md
View file
Open in desktop
Original file line number Diff line number Diff line change
@@ -1,13 +1,13 @@
# Goal
Improve performance or memory usage of `src` and related code (tests, configs, dependencies) without causing regressions.
Improve performance or memory usage of `src`, `website/server`, and related code (tests, configs, dependencies) without causing regressions.

Think broadly — algorithm changes, architectural restructuring, parallelization, caching strategies, library replacements, dependency upgrades, and I/O reduction are all fair game. Small logic tweaks that only shave a few milliseconds on a 1000-file run are not worth pursuing. Aim for changes with meaningful, measurable impact.

# Steps

## Investigation & Planning

Spawn an agent team to investigate efficiently and thoroughly, then form an improvement plan.
Spawn 10 agents in parallel to investigate efficiently and thoroughly, then form an improvement plan.
Copy link
Copy Markdown
Contributor

@gemini-code-assist gemini-code-assist Bot Mar 21, 2026

Choose a reason for hiding this comment

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

medium

Hardcoding the number of parallel agents to 10 might not be optimal for all environments, as it doesn't account for varying system resources. It would be more flexible to specify this as a maximum number of agents rather than a fixed count.

Suggested change
Spawn 10 agents in parallel to investigate efficiently and thoroughly, then form an improvement plan.
Spawn up to 10 agents in parallel to investigate efficiently and thoroughly, then form an improvement plan.

Even if multiple improvements are identified, scope the work to what fits in a single PR — focus on the highest-impact change only.

## Implementation
Expand Down
Loading