Memory grows day after day
Weik.io 2026.2A copy of the deployment needs 20 % more memory over 3 to 7 days, or its heap is on course to reach its limit within a week.
| Kind | Severity | Who sees it |
|---|---|---|
deployment- |
Warning | Everyone who can read the deployment |
Its row in the problem list has a figure such as growing 38 MB a day.
What it means#
A copy of the deployment uses more memory every day, which usually means something in its routes keeps objects it no longer needs. If nothing changes, the process runs out of memory and restarts.
What raises it#
Weik.io checks each copy over the latest 3 to 7 whole days since it last started. The first two hours after a start don’t count, so a cache that fills on its first day raises nothing.
The problem shows when the lowest memory of each day grows by 20 % or more over those days. It also shows when the heap that stays in use after garbage collection is on course to reach its limit within 7 days. The detail shows whether the memory growth or the heap raised it.
You don’t see this problem on an installation set up without the hub’s metric store.
What to check#
Chart the memory over a week:
$ weikio metrics <project>/<integration> --env <environment> --name memory --since 7dSee which agents run the copies and when each started:
$ weikio describe deployment <project>/<integration> --env <environment>How to fix it#
Look in the routes for something that keeps growing:
- An aggregation that never completes
- An idempotent repository or cache without a size limit
- A collection that a processor keeps adding to
Fix the route and publish a new version. Until then, a restart frees the memory for a while:
$ weikio restart <project>/<integration> --env <environment>