0 Fork 0

mirror of https://github.com/yamadashy/repomix.git synced 2026-10-08 17:49:11 +02:00

Files

T

History

Kazuki YamadaandClaude Opus 4.6 d659865f35 fix(scripts): Compare post-warmup baseline in memory test final analysis

The final analysis compared iteration 0 (cold start, ~20MB heap) against
the final measurement, causing false "significant memory growth" warnings
on short CI runs (50 iterations). Now uses the average of post-warmup
entries as baseline, matching how the mid-run trend analysis already works.

Co-Authored-By: Claude Opus 4.6 (1M context) <noreply@anthropic.com>

2026-04-03 13:05:56 +09:00

src

fix(scripts): Compare post-warmup baseline in memory test final analysis

2026-04-03 13:05:56 +09:00

.gitignore

refactor: Move memory benchmarks from benchmarks/ to scripts/

2025-09-01 23:29:47 +09:00

.npmrc

chore(security): Add min-release-age to sub-package .npmrc files

2026-03-21 18:45:30 +09:00

package-lock.json

chore(deps): update dependency @types/node to ^24.12.0

2026-03-21 05:00:41 +00:00

package.json

chore(deps): update dependency @types/node to ^24.12.0

2026-03-21 05:00:41 +00:00

README.md

refactor: Move memory benchmarks from benchmarks/ to scripts/

2025-09-01 23:29:47 +09:00

tsconfig.json

refactor: Move memory benchmarks from benchmarks/ to scripts/

2025-09-01 23:29:47 +09:00

README.md

Memory Benchmarks

Memory usage monitoring tools for repomix.

Setup

cd scripts/memory
npm install

Quick Start

# Quick memory leak check
npm run leak:quick

# Detailed analysis
npm run leak:analyze

Available Scripts

npm run leak:quick - Fast leak detection (20 iterations)
npm run leak:watch - Continuous monitoring
npm run leak:analyze - Comprehensive analysis with reports

Understanding Results

Heap Memory: JavaScript objects (should stabilize)
RSS Memory: Total process memory (watch for growth > 100%)

Look for consistent upward trends that indicate memory leaks.