ipx-directory holds about 900 MB, and nothing shows whether it climbs #220
Reference in New Issue
Block a user
Delete Branch "%!s()"
Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?
On 2026-10-13 at 12:00 UTC, 15 hours after it started,
ipx-directoryhad a resident size of 937 MB (docker top ipx-directory -o pid,rss;docker statssaid 920 MiB). iPX, which does far more work, had 626 MiB, and ipx-web 46 MiB. The directory lists 1,471 feeds and checks 25 at a time every six hours.It has no metrics (no
/metrics, no scrape job), so there is no history to say whether it climbs steadily (a leak, such as feed bodies or responses kept), stepped up once (a large feed read whole into memory, which the allocator keeps), or sits there from the start. The size was unchanged over a few minutes of sampling.Worth: sampling it over a day, or giving it a resident-size gauge the way ipx has
ipx_process_resident_bytes, and checking whether the refresher reads feed bodies without a size limit.Closed without a fix: the prod check covers ipx itself, not the other containers or the self-hosted tooling, and those are not filed here.