- Reorganize v3/ into implementation/ subfolders: - planning/, architecture/, migration/, integration/ - security/, adrs/, research/, swarm-plans/ - Add 15-agent concurrent swarm implementation plans: - SWARM-OVERVIEW.md: Hierarchical mesh topology, 4 phases - AGENT-SPECIFICATIONS.md: 15 agent configs with capabilities - TDD-LONDON-SCHOOL-PLAN.md: Mock-first TDD methodology - BENCHMARK-OPTIMIZATION.md: Performance targets (2.49x-7.47x) - DEPLOYMENT-PLAN.md: Release strategy, CI/CD, rollback - GITHUB-ISSUE-TRACKING.md: Issue workflow with agent replies - Update .claude/settings.json with proper hooks format - Add bash aliases for claude --dangerously-skip-permissions 🤖 Generated with [Claude Code](https://claude.com/claude-code) Co-Authored-By: Claude Opus 4.5 <noreply@anthropic.com>
AgentDB Performance Testing Suite
Comprehensive performance testing and optimization tools for AgentDB v1.3.9 integration.
Overview
This suite validates the claimed performance improvements of AgentDB over the current claude-flow memory system:
- 150x faster search with HNSW indexing
- 500x faster batch inserts
- 12,500x faster large-scale queries
- 4-32x memory reduction with quantization
Test Suites
1. Baseline Performance (baseline/current-system.js)
Measures current system performance to establish baselines:
- Pattern search latency (linear scan)
- Batch insert throughput
- Large-scale query performance (10K-100K vectors)
- Memory usage patterns
Run:
node tests/performance/baseline/current-system.js
Output: docs/agentdb/benchmarks/baseline-report.json
2. AgentDB Performance Validation (agentdb/agentdb-perf.js)
Validates AgentDB performance claims:
- HNSW search performance (<100µs target)
- Batch insert performance (<2ms for 100 vectors)
- Large-scale queries (<10ms for 1M vectors)
- Quantization memory efficiency
Run:
node tests/performance/agentdb/agentdb-perf.js
Output: docs/agentdb/benchmarks/agentdb-report.json
Prerequisites: Agent 1 must complete AgentDB implementation first.
3. HNSW Optimization (agentdb/hnsw-optimizer.js)
Analyzes HNSW configurations to find optimal settings:
- Tests different M, efConstruction, efSearch values
- Measures build time vs search accuracy trade-offs
- Calculates recall@K for accuracy validation
- Recommends configurations for different use cases
Run:
node tests/performance/agentdb/hnsw-optimizer.js
Output: docs/agentdb/benchmarks/hnsw-optimization.json
Recommendations:
- Fastest search
- Highest recall
- Best balance
- Fastest build
- Most efficient (QPS/Memory)
4. Load Testing (agentdb/load-test.js)
Tests system under realistic production loads:
- Scalability: 1K → 1M vectors
- Concurrent Access: 1-50 simultaneous queries
- Stress Test: Sustained high load (30s+)
- Resource Limits: CPU and memory constraints
Run:
node tests/performance/agentdb/load-test.js
Output: docs/agentdb/benchmarks/load-test-report.json
Tests:
- Insertion throughput at scale
- Query latency under load
- Concurrent query handling
- System stability over time
5. Memory Profiling (agentdb/memory-profile.js)
Analyzes memory usage patterns and efficiency:
- Baseline memory usage
- Quantization impact (binary, scalar, product)
- Memory leak detection
- Peak memory under load
Run with GC exposure for accurate profiling:
node --expose-gc tests/performance/agentdb/memory-profile.js
Output: docs/agentdb/benchmarks/memory-profile-report.json
Analysis:
- Bytes per vector
- Memory scaling (100K, 1M, 10M vectors)
- Quantization savings percentages
- Leak detection (trend analysis)
Running All Tests
Sequential Execution
# 1. Baseline (run first, before AgentDB implementation)
node tests/performance/baseline/current-system.js
# 2. Wait for Agent 1 to complete AgentDB implementation
# 3. Run AgentDB benchmarks
node tests/performance/agentdb/agentdb-perf.js
node tests/performance/agentdb/hnsw-optimizer.js
node tests/performance/agentdb/load-test.js
node --expose-gc tests/performance/agentdb/memory-profile.js
Automated Suite
# Create test runner script
npm run benchmark:all
Results & Reports
All benchmark results are saved to docs/agentdb/benchmarks/:
docs/agentdb/benchmarks/
├── baseline-report.json # Current system baseline
├── agentdb-report.json # AgentDB performance validation
├── hnsw-optimization.json # HNSW configuration analysis
├── load-test-report.json # Load testing results
└── memory-profile-report.json # Memory profiling analysis
Interpreting Results
Performance Metrics
Query Latency:
- Target: <100µs (0.1ms) for HNSW search
- Current: ~15ms for 10K vectors (linear scan)
- Improvement: Should be 150x faster
Batch Insert:
- Target: <2ms for 100 vectors
- Current: ~1000ms for 100 vectors
- Improvement: Should be 500x faster
Large Queries:
- Target: <10ms for 1M vectors
- Current: ~125 seconds for 1M vectors
- Improvement: Should be 12,500x faster
Memory Metrics
Quantization Savings:
- None: Baseline
- Binary: ~75% savings (4x capacity)
- Scalar: ~87.5% savings (8x capacity)
- Product: ~96.875% savings (32x capacity)
Quality Metrics
Recall@K:
- Target: >95% for production
- Acceptable: >90% for most use cases
- Trade-off: Higher M and efSearch = better recall but slower
Configuration Recommendations
Based on benchmark results, choose configuration:
Development
{ M: 16, efConstruction: 200, efSearch: 50, quantization: null }
Production (Small-Medium)
{ M: 16, efConstruction: 200, efSearch: 100, quantization: 'binary' }
Production (Large Scale)
{ M: 32, efConstruction: 400, efSearch: 200, quantization: 'product' }
High Performance (Low Latency)
{ M: 64, efConstruction: 800, efSearch: 400, quantization: null }
Troubleshooting
"AgentDB not available" Error
Cause: Agent 1 hasn't completed implementation yet.
Solution: Wait for Agent 1 to implement core AgentDB integration, then run tests.
High Memory Usage
Cause: Testing with large datasets without quantization.
Solution:
- Enable quantization:
quantization: { type: 'binary' } - Reduce test dataset sizes
- Run with
--max-old-space-size=8192for Node.js
"Garbage collection not exposed" Warning
Cause: Running memory profiler without --expose-gc flag.
Solution: Run with: node --expose-gc tests/performance/agentdb/memory-profile.js
Benchmark Timeouts
Cause: Large-scale tests taking too long.
Solution:
- Reduce dataset sizes in test configuration
- Increase Node.js timeout
- Run on more powerful hardware
Contributing
When adding new benchmarks:
- Follow existing patterns for consistency
- Generate JSON reports for automated analysis
- Include clear console output for human readability
- Document new metrics and thresholds
- Update this README
References
- AgentDB Documentation: https://github.com/rUv-Swarm/agentdb
- HNSW Algorithm: https://arxiv.org/abs/1603.09320
- Vector Quantization: https://en.wikipedia.org/wiki/Vector_quantization
- Claude-Flow Integration Plan:
/docs/AGENTDB_INTEGRATION_PLAN.md - Production Readiness:
/docs/agentdb/PRODUCTION_READINESS.md