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

[Jesse]

@Manu

Yes, there are many ideas. Subnets can be split , we can imagine further improvements to the scheduler, we could add other ways for canisters to request priority on busy subnets, we could further increase the compute capacity of subnets by using more cores, make migrating canisters to a different subnet easier, etc.

I have canisters that control neurons via ECDSA signed HTTPS outcalls which requires the public keys of canisters. When canisters are migrated to other subnets, does this effect their key signatures in any way? I want to confirm that when canister migration becomes available, I’ll be able to migrate canisters that control neurons without losing access to those neurons.