-
Will the existing Canisters scale in the subnet affect the running speed of the contract and the future space?
-
If these problems exist, is there any way to avoid them, because our application is deployed to a relatively large subnet (https://dashboard.internetcomputer.org/subnet/opn46-zyspe-hhmyp-4zu6u-7sbrh-dok77-m7dch-im62f-vyimr-a3n2c-4ae)
-
Once our application is fully released, the user scale will be very large. Do we need to migrate the application to a young subnet?
- Yes. Every subnet has limited resources and using resources puts that subnet closer to capacity. A lot of discussion on this topic is ongoing here
- As you can read in the thread I linked above, it is possible to avoid some of them, e.g. with a compute allocation.
- Depends on the scale and your requirements. You many even have to scale across multiple subnets if you reach a certain size. A subnet is inherently bound to what a single machine could accomplish on its own
Thank you, looking forward to the release of container migration functionality.