A canister's main memory is capped by its own memory limit (4 GiB when it sets none), while its secondary memory can grow into the storage the engine has for apps.
- Open Software canisters and click the canister.
- Under Storage in the top card, read how full its main memory is: …% of heap limit.
- Open the Metrics tab. Memory shows the Current footprint (App state plus Installed code), Main memory against its canister limit, and how much Secondary memory is allocated.
Good to know
- Main memory is the canister's primary WASM memory. It does not overflow into secondary memory: an app that outgrows it has to keep its data in secondary (stable) memory by design.
- The bar turns amber from 75% and red from 90%. From 75% the page also warns Main memory at …% of the canister limit. Review the app's storage design.
- Secondary memory is optional explicit storage. It's bounded by the engine's app storage, which every canister on the engine shares, and by about 500 GiB per canister.
- The Storage column on Software canisters is each canister's whole memory footprint.
- The console has no per-canister memory or CPU setting to change. What a canister spends on computation shows as Compute under Platform resource use on the Metrics tab.