TEST-INFRA: [missing-test-levels] Add ASV performance benchmarks for the infrastructure module #3772

Open
opened 2026-04-05 22:36:11 +00:00 by freemo · 1 comment
Owner

Metadata

  • Branch: test/missing-test-levels-infrastructure-asv-performance-benchmarks
  • Commit Message: test(infrastructure): add ASV performance benchmarks for the infrastructure module
  • Milestone: N/A — Backlog (see note below)
  • Parent Epic: #1678

Backlog note: This issue was discovered during autonomous operation
on milestone Test Infrastructure. It does not block milestone completion and has been
placed in the backlog for human review and future milestone assignment.

Background and Context

The infrastructure module in src/cleveragents/infrastructure is missing ASV (airspeed velocity) performance benchmarks. Per the project testing strategy, every module must have performance benchmarks to track and prevent performance regressions over time.

The infrastructure module provides the foundational runtime layer of the CleverAgents platform, including the LSP Runtime (which manages language server lifecycles, workspace mapping, and file synchronisation), core registries (Resource Registry, Tool Registry, Skill Registry, Actor Registry, LSP Registry), and the A2A protocol communication backbone. Without ASV benchmark coverage, performance regressions in these critical infrastructure components — such as LSP server startup latency, registry lookup times, and A2A protocol throughput — may go undetected across releases.

This issue tracks the work to bring the infrastructure module into compliance with the ASV performance benchmark requirement.

Subtasks

  • Audit the infrastructure module's critical code paths to identify all functions and operations requiring ASV benchmark coverage (e.g., LSP runtime lifecycle, registry operations, A2A protocol handling)
  • Create a new benchmark file in benchmarks/infrastructure/ for the infrastructure module
  • Add ASV performance benchmarks for the critical functions in the infrastructure module
  • Ensure the benchmarks run successfully and produce meaningful, reproducible results
  • Verify benchmarks integrate correctly with the existing ASV configuration
  • Run nox (all default sessions), fix any errors
  • Verify coverage >= 97% via nox -s coverage_report

Definition of Done

  • ASV benchmarks for the infrastructure module are implemented and passing
  • The new benchmarks provide adequate performance coverage for the module's critical code paths
  • A Git commit is created where the first line of the commit message matches the Commit Message in Metadata exactly, followed by a blank line, then additional lines providing relevant details about the implementation
  • The commit is pushed to the remote on the branch matching the Branch in Metadata exactly
  • The commit is submitted as a pull request to master, reviewed, and merged before this issue is marked done
  • All nox stages pass
  • Coverage >= 97%

Automated by CleverAgents Bot
Supervisor: Test Infrastructure | Agent: ca-new-issue-creator

## Metadata - **Branch**: `test/missing-test-levels-infrastructure-asv-performance-benchmarks` - **Commit Message**: `test(infrastructure): add ASV performance benchmarks for the infrastructure module` - **Milestone**: N/A — Backlog (see note below) - **Parent Epic**: #1678 > **Backlog note:** This issue was discovered during autonomous operation > on milestone Test Infrastructure. It does not block milestone completion and has been > placed in the backlog for human review and future milestone assignment. ## Background and Context The `infrastructure` module in `src/cleveragents/infrastructure` is missing ASV (airspeed velocity) performance benchmarks. Per the project testing strategy, every module must have performance benchmarks to track and prevent performance regressions over time. The `infrastructure` module provides the foundational runtime layer of the CleverAgents platform, including the LSP Runtime (which manages language server lifecycles, workspace mapping, and file synchronisation), core registries (Resource Registry, Tool Registry, Skill Registry, Actor Registry, LSP Registry), and the A2A protocol communication backbone. Without ASV benchmark coverage, performance regressions in these critical infrastructure components — such as LSP server startup latency, registry lookup times, and A2A protocol throughput — may go undetected across releases. This issue tracks the work to bring the `infrastructure` module into compliance with the ASV performance benchmark requirement. ## Subtasks - [ ] Audit the `infrastructure` module's critical code paths to identify all functions and operations requiring ASV benchmark coverage (e.g., LSP runtime lifecycle, registry operations, A2A protocol handling) - [ ] Create a new benchmark file in `benchmarks/infrastructure/` for the `infrastructure` module - [ ] Add ASV performance benchmarks for the critical functions in the `infrastructure` module - [ ] Ensure the benchmarks run successfully and produce meaningful, reproducible results - [ ] Verify benchmarks integrate correctly with the existing ASV configuration - [ ] Run `nox` (all default sessions), fix any errors - [ ] Verify coverage >= 97% via `nox -s coverage_report` ## Definition of Done - [ ] ASV benchmarks for the `infrastructure` module are implemented and passing - [ ] The new benchmarks provide adequate performance coverage for the module's critical code paths - [ ] A Git commit is created where the **first line** of the commit message matches the Commit Message in Metadata exactly, followed by a blank line, then additional lines providing relevant details about the implementation - [ ] The commit is pushed to the remote on the branch matching the **Branch** in Metadata exactly - [ ] The commit is submitted as a **pull request** to `master`, reviewed, and **merged** before this issue is marked done - [ ] All nox stages pass - [ ] Coverage >= 97% --- **Automated by CleverAgents Bot** Supervisor: Test Infrastructure | Agent: ca-new-issue-creator
Author
Owner

Issue triaged by project owner:

  • State: Verified
  • Priority: Backlog (confirmed)
  • Story Points: 5 — L — Requires auditing infrastructure module critical paths, creating benchmark file, and implementing meaningful ASV benchmarks.
  • MoSCoW: Could Have — Performance benchmarks are valuable for regression detection but are not blocking any milestone. The spec says modules "must" have benchmarks, but this is a testing completeness concern, not a functional requirement.
  • Parent Epic: #1678

Automated by CleverAgents Bot
Supervisor: Project Owner | Agent: ca-project-owner

Issue triaged by project owner: - **State**: Verified - **Priority**: Backlog (confirmed) - **Story Points**: 5 — L — Requires auditing infrastructure module critical paths, creating benchmark file, and implementing meaningful ASV benchmarks. - **MoSCoW**: Could Have — Performance benchmarks are valuable for regression detection but are not blocking any milestone. The spec says modules "must" have benchmarks, but this is a testing completeness concern, not a functional requirement. - **Parent Epic**: #1678 --- **Automated by CleverAgents Bot** Supervisor: Project Owner | Agent: ca-project-owner
Sign in to join this conversation.
No milestone
No project
No assignees
1 participant
Notifications
Due date
The due date is invalid or out of range. Please use the format "yyyy-mm-dd".

No due date set.

Reference
cleveragents/cleveragents-core#3772
No description provided.