The contract I developed has been released, but the execution update is very slow?

[haida]

The contract I developed has been released, but the execution update is very slow?

We used motoko to develop a system for more than 2 years, which has been released online today, but we found that the execution update call is very slow (just a simple data update), which has exceeded 10 seconds, and even timed out. However, we do not have this problem in the local development environment, and the general update call can be completed in 1-2 seconds.
Can it be adjusted, or is it related to the subnet selection?
Such an execution speed cannot be used in a production environment at all, which makes us feel very scared…
Hope to get effective suggestions, thank you!

Main canisterId “wk3vs-2aaaa-aaaak-qlowa-cai”
Subnet id: opn46-zyspe-hhmyp-4zu6u-7sbrh-dok77-m7dch-im62f-vyimr-a3n2c-4ae

[Severin]

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

Hi everybody! In the recent weeks, we’ve seen the demand for computation on ICP significantly increase. This is of course great news, but also leads to some challenges. We now see that there are quite some subnets that are running at or almost at maximum compute capacity. This means that canisters have to wait for their turn to compute and therefore messages are processed with much higher latency. You may notice ingress messages get rejected with an error saying “timed out waiting to start execu…

[haida]

This phenomenon happens very frequently. I plan to migrate to another subnet. Can the CanisterId be maintained after the migration? Can all sub-Canisters be migrated at the same time? However, I have not found any relevant tutorials.

[h1teshtr1path1]

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

Yes, your canister id matters for the key derivation, so simply reinstalling your canister on a different subnet while using threshold signatures is not going to work. Subnet splitting makes sure all canister ids are kept, so that this is not a problem. The protocol does not offer an easy way to transfer your canister without changing id yet, so this is a downside you have to consider if you manually move your canister. I hope we can address this limitation with future improvements.