Memory costs on ICP are changing, so you might be thinking “what does this mean for my cycle bill”?
We were wondering the same thing 
, so we built a dedicated Memory Price Change view into CycleOps that teams can use to quickly understand the impact of the upcoming ICP protocol memory pricing update.
Not already using CycleOps?, hook up your dapp in less than 10 minutes!
Account Wide & Per Canister Memory Cost Metrics
The new memory cost page displays estimates on an account-wide and per-canister basis before and after the protocol change. Keep in mind that these estimates will change as new canisters are added and as existing canisters use more memory.
These account-wide estimates include:
- Before/After memory cost
- Memory cost increase amount
- Total cycle costs (memory + compute), and the percent change in those monthly totals after memory costs increase
Additionally, you’ll find a per-canister cost impact table sorted by canisters with the largest memory-related cost increase.
Closing thoughts
While a 2.5× change sounds large in isolation, every application and canister has a different cost breakdown. Understanding projected costs can help you identify your most impacted services and realize future cost savings.
Have feedback or questions about the new memory cost tool? Let us know!
For more on how to discover the new memory cost explorer and other CycleOps updates, check out our changelog