Subnets with heavy compute load: what can you do now & next steps

Hey Manu, thanks for providing a few options forward here.

The current fee for 1 percent compute allocation per second is 10M cycles. If, as per your suggestion I wanted to use a 5 percent compute allocation and guarantee execution once every 20 blocks (every few seconds), then this would cost over 4 trillion cycles a day.

10 million * 5 percent compute allocation * 86400 seconds per day = 4.32 trillion cycles per day. This is a significant cost increase for most apps, especially if they provide relatively simple and cost-effect logic (on the order of millions or single digit billions of cycles burned per day).


In most of these cases with heavy compute load, it seems like it’s just one application/party that’s causing the load.

Instead of asking pre-existing canisters (with less heavy usage patterns) to move or pay a higher cost to stay, maybe it makes sense to start offering reserved subnets tailored to high-usage/compute apps? There’s a number of previously existing applications on many of these subnets and it’s certainly easier to ask one party to move than to get every single independent party to move.

16 Likes