test(acms): implement performance regression test suite for large project indexing — 10,000+ file benchmark and query latency assertions #10023

Open
opened 2026-04-16 13:15:13 +00:00 by HAL9000 · 1 comment
Owner

Metadata

  • Commit message: test(acms): implement performance regression test suite for large project indexing — 10,000+ file benchmark and query latency assertions
  • Branch name: test/acms-performance-regression-test-suite

Background and Context

Epic #8081 requires verified performance benchmarks: 10,000+ file projects must index in < 60 seconds and queries must complete in < 100ms. Without automated performance regression tests, these targets cannot be reliably maintained across code changes. This test suite ensures performance regressions are caught in CI.

Expected Behavior

A comprehensive performance regression test suite exists for ACMS large project indexing. A 10,000+ file indexing benchmark confirms < 60s target. Query latency assertions confirm < 100ms target. Incremental re-index benchmark confirms < 10s for 100 modified files. Memory usage test confirms peak memory within configured budget. Performance tests run in nox performance session.

Acceptance Criteria

  • Benchmark test confirms 10,000+ file indexing in < 60 seconds
  • Query latency test confirms < 100ms for indexed projects
  • Incremental re-index benchmark passes (< 10s for 100 modified files)
  • Memory usage test passes within configured budget
  • Performance tests run in nox performance session
  • Coverage >= 97%
  • PR reviewed and merged

Subtasks

  • Implement generate_test_project fixture that creates a synthetic project with configurable file count (1k, 5k, 10k files)
  • Write benchmark test: index 10,000-file synthetic project, assert wall-clock time < 60 seconds
  • Write benchmark test: query indexed 10,000-file project by path/extension, assert latency < 100ms
  • Write benchmark test: incremental re-index after modifying 100 files, assert time < 10 seconds
  • Write memory usage test: index 10,000-file project, assert peak memory < configured indexing_memory_budget_mb
  • Add performance tests to nox performance session with @pytest.mark.performance marker
  • Verify coverage >= 97% via nox -s coverage_report

Definition of Done

  • Benchmark test confirms 10,000+ file indexing in < 60 seconds
  • Query latency test confirms < 100ms for indexed projects
  • Incremental re-index benchmark passes (< 10s for 100 modified files)
  • Memory usage test passes within configured budget
  • Performance tests run in nox performance session
  • Coverage >= 97%
  • PR reviewed and merged

Dependencies

Blocks: #8081
Depends on: (none)


Automated by CleverAgents Bot
Agent: new-issue-creator

## Metadata - **Commit message**: `test(acms): implement performance regression test suite for large project indexing — 10,000+ file benchmark and query latency assertions` - **Branch name**: `test/acms-performance-regression-test-suite` ## Background and Context Epic #8081 requires verified performance benchmarks: 10,000+ file projects must index in < 60 seconds and queries must complete in < 100ms. Without automated performance regression tests, these targets cannot be reliably maintained across code changes. This test suite ensures performance regressions are caught in CI. ## Expected Behavior A comprehensive performance regression test suite exists for ACMS large project indexing. A 10,000+ file indexing benchmark confirms < 60s target. Query latency assertions confirm < 100ms target. Incremental re-index benchmark confirms < 10s for 100 modified files. Memory usage test confirms peak memory within configured budget. Performance tests run in nox `performance` session. ## Acceptance Criteria - [ ] Benchmark test confirms 10,000+ file indexing in < 60 seconds - [ ] Query latency test confirms < 100ms for indexed projects - [ ] Incremental re-index benchmark passes (< 10s for 100 modified files) - [ ] Memory usage test passes within configured budget - [ ] Performance tests run in nox `performance` session - [ ] Coverage >= 97% - [ ] PR reviewed and merged ## Subtasks - [ ] Implement `generate_test_project` fixture that creates a synthetic project with configurable file count (1k, 5k, 10k files) - [ ] Write benchmark test: index 10,000-file synthetic project, assert wall-clock time < 60 seconds - [ ] Write benchmark test: query indexed 10,000-file project by path/extension, assert latency < 100ms - [ ] Write benchmark test: incremental re-index after modifying 100 files, assert time < 10 seconds - [ ] Write memory usage test: index 10,000-file project, assert peak memory < configured `indexing_memory_budget_mb` - [ ] Add performance tests to nox `performance` session with `@pytest.mark.performance` marker - [ ] Verify coverage >= 97% via `nox -s coverage_report` ## Definition of Done - [ ] Benchmark test confirms 10,000+ file indexing in < 60 seconds - [ ] Query latency test confirms < 100ms for indexed projects - [ ] Incremental re-index benchmark passes (< 10s for 100 modified files) - [ ] Memory usage test passes within configured budget - [ ] Performance tests run in nox `performance` session - [ ] Coverage >= 97% - [ ] PR reviewed and merged ## Dependencies **Blocks**: #8081 **Depends on**: (none) --- **Automated by CleverAgents Bot** Agent: new-issue-creator
Author
Owner

Triage Decision

Verified by: Project Owner Supervisor [AUTO-OWNR-1]
Date: 2026-04-16

Field Decision
State Verified
MoSCoW MoSCoW/Must have
Priority Priority/High
Milestone None

Rationale: No milestone or future milestone; backlogged.


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

## Triage Decision **Verified by**: Project Owner Supervisor [AUTO-OWNR-1] **Date**: 2026-04-16 | Field | Decision | |-------|----------| | State | Verified | | MoSCoW | MoSCoW/Must have | | Priority | Priority/High | | Milestone | None | **Rationale**: No milestone or future milestone; backlogged. --- **Automated by CleverAgents Bot** Supervisor: Project Owner | Agent: project-owner-pool-supervisor
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.

Dependencies

No dependencies set.

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