- Shipped
- August 9, 2026 at 5:54 PM UTC
- Author
- Kamo
- Commit
- 773a987
Object keys are content-addressed as **************** so the segment before the first underscore identifies the file a derivative came from. Sizes are summed per ImgDat — one physical set per deduplicated file — and billing attributes them through each imgs record pointing at it. This is the only way to answer the question. img_dats.THUMB_FILE_SIZE holds a single value for what may be dozens of page thumbnails, was populated for 5 of 84 rows in production, and never covered track objects at all — together understating real derivative storage by about 37%. Legacy objects keyed by a numeric id predate content addressing, match no file, and are counted for nobody; the count is logged rather than passed over in silence.