🛑 The Problem
We claim our streaming architecture uses constant memory (O(1) space complexity) regardless of repository size. However, per Directive 002 (Reality Wins), we must prove this with hard evidence. We need an automated script that monitors the Node.js V8 engine's heap usage during a massive ingestion.
💡 The Solution
Write a Node.js profiling script that runs a test ingestion of a massive repo (like torvalds/linux or facebook/react) and logs the memory heap statistics every 500ms.
🛠️ Implementation Details
- Create
scripts/benchmark-memory.js.
- Use Node's built-in
v8 module: v8.getHeapStatistics().
- Trigger the Octokit streaming ingestion locally.
- Log the
used_heap_size to a CSV file or console table.
- Assert that the
used_heap_size never exceeds 300MB at any point during the hour-long sync.
✅ Acceptance Criteria
Ready to tackle this? Comment .take below to get automatically assigned!
🛑 The Problem
We claim our streaming architecture uses constant memory (O(1) space complexity) regardless of repository size. However, per Directive 002 (Reality Wins), we must prove this with hard evidence. We need an automated script that monitors the Node.js V8 engine's heap usage during a massive ingestion.
💡 The Solution
Write a Node.js profiling script that runs a test ingestion of a massive repo (like
torvalds/linuxorfacebook/react) and logs the memory heap statistics every 500ms.🛠️ Implementation Details
scripts/benchmark-memory.js.v8module:v8.getHeapStatistics().used_heap_sizeto a CSV file or console table.used_heap_sizenever exceeds 300MB at any point during the hour-long sync.✅ Acceptance Criteria
docs/PRODUCT_TRUTH.md.Ready to tackle this? Comment
.takebelow to get automatically assigned!