Summary

Standardize the location of BASELINE.md performance documentation to docs/performance/BASELINE.md across all ecosystem systems, eliminating inconsistency between benchmarks/ and docs/performance/ locations.

Background (Why)

• BASELINE.md files exist in inconsistent locations across systems
• Some systems have BASELINE.md in benchmarks/, others in docs/performance/
• Some systems have duplicates in both locations
• Inconsistent location makes it difficult to find performance documentation
• Creates confusion for developers working across multiple systems

Current inconsistent locations:

common_system/        - docs/BENCHMARKS.md (no BASELINE.md)
thread_system/        - benchmarks/BASELINE.md, tests/benchmarks/BASELINE.md
logger_system/        - benchmarks/BASELINE.md
container_system/     - benchmarks/BASELINE.md
monitoring_system/    - benchmarks/BASELINE.md, docs/performance/BASELINE.md (DUPLICATE)
database_system/      - benchmarks/BASELINE.md, docs/performance/BASELINE.md (DUPLICATE)
network_system/       - BASELINE.md (root), benchmarks/BASELINE.md

Scope (What)

Current State

Proposed State

Standard Structure

<system>/
├── benchmarks/
│   ├── README.md            # Benchmark code documentation
│   └── (benchmark source files)
└── docs/
    └── performance/
        ├── BASELINE.md      # PRIMARY - Performance baseline results
        └── TUNING.md        # Performance tuning guide (if exists)

Impact Analysis (Where)

Files to Modify by System

Cross-Reference Updates

For each system:

• Update benchmarks/README.md to link to docs/performance/BASELINE.md
• Update any README.md references to BASELINE.md location
• Update CI/CD workflows that reference BASELINE.md

Implementation Plan (How)

Phase 1: Create Target Directories

1. Ensure docs/performance/ directory exists in all systems
2. Create directory if missing

Phase 2: thread_system

3. Move benchmarks/BASELINE.md to docs/performance/BASELINE.md
4. Delete tests/benchmarks/BASELINE.md (duplicate)
5. Update benchmarks/README.md with link

Phase 3: logger_system

6. Move benchmarks/BASELINE.md to docs/performance/BASELINE.md
7. Update benchmarks/README.md with link

Phase 4: container_system

8. Move benchmarks/BASELINE.md to docs/performance/BASELINE.md
9. Update benchmarks/README.md with link

Phase 5: monitoring_system

10. Compare both BASELINE.md files
11. Merge unique content into docs/performance/BASELINE.md
12. Delete benchmarks/BASELINE.md
13. Update benchmarks/README.md with link

Phase 6: database_system

14. Compare both BASELINE.md files
15. Merge unique content into docs/performance/BASELINE.md
16. Delete benchmarks/BASELINE.md
17. Update benchmarks/README.md with link

Phase 7: network_system

18. Consolidate root and benchmarks/ BASELINE.md
19. Move to docs/performance/BASELINE.md
20. Delete duplicates
21. Update references

Phase 8: Verification

22. Verify BASELINE.md exists in docs/performance/ for all systems
23. Verify no duplicate BASELINE.md files remain
24. Verify all links are updated

Acceptance Criteria

• All systems have BASELINE.md in docs/performance/
• No BASELINE.md in benchmarks/ directory (only links)
• No BASELINE.md at root level in any system
• All benchmarks/README.md files link to correct location
• All main README.md files have correct BASELINE.md links
• No duplicate BASELINE.md files
• CI/CD workflows updated if they reference BASELINE.md

Related Issues

• Part of Epic: docs: [Epic] Standardize documentation structure across all ecosystem systems #303

Labels

• documentation
• enhancement
• standardization