From 2c509b51fc9462c43d0e12a6afaa039d52c7335a Mon Sep 17 00:00:00 2001 From: Hugh Kaznowski Date: Sat, 5 Sep 2026 18:38:29 +0100 Subject: [PATCH] Remove tickets/011-approximate-heap-tracker.md (implemented) Co-Authored-By: Claude Sonnet 5 Claude-Session: https://claude.ai/code/session_01XFUNZwCvz3kcod3352ZR2o --- tickets/011-approximate-heap-tracker.md | 8 -------- 1 file changed, 8 deletions(-) delete mode 100644 tickets/011-approximate-heap-tracker.md diff --git a/tickets/011-approximate-heap-tracker.md b/tickets/011-approximate-heap-tracker.md deleted file mode 100644 index c4d403e..0000000 --- a/tickets/011-approximate-heap-tracker.md +++ /dev/null @@ -1,8 +0,0 @@ -# Add approximate heap/memory tracker for ingested logs - -An approximate heap tracker should exist. For each log ingested, its bytes are counted. If it's ever dropped, its bytes are subtracted. The size can be displayed on the frontend as comma-separated bytes. - -## Acceptance criteria -- Ingestion path increments a running byte counter by each log's approximate size when ingested. -- Eviction/drop path decrements the counter by that log's size when it's dropped. -- Current total is exposed via the API and displayed on the frontend, formatted with comma separators (e.g. "12,345,678 bytes").