-
Notifications
You must be signed in to change notification settings - Fork 317
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
feat: Reduce DTS slice limit for regular messages on system subnets #621
Conversation
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
🚀
Are we doing this now despite delaying changing the checkpoint interval on the NNS subnet until after the scheduled II subnet recovery? |
@schneiderstefan Yes, if you notice, I'm only changing the slice limit for regular messages. Given a 2B slice limit and the 50B total limit, we would have at most 25 slices. That's still quite fine even with a 200 rounds checkpoint interval. Increasing the checkpoint interval blocks decreasing the slice limit for |
Marked as |
…lts set at system level) (#650) Deterministic Time Slicing, which allows large messages to execute across multiple rounds, was being tested in advance of releasing it as system settings. Now that t[he system settings are being updated](#621), we no longer need special configuration to test this on system subnets.
Tests were successful. |
Disable DTS in `drun` for system subnets to enable deterministic debug output testing. **Background information**: DTS aborts uncompleted messsages if they reach a checkpoint and retries them later. However, debug prints of such DTS-aborted executions leak, which leads to non-deterministic debug outputs and can disturb testing with `drun`. Therefore, disable DTS on system subnets in `drun` for deterministic debug outputs as required by Motoko's tests. This testing issue has become noticeable with #621.
…lts set at system level) (dfinity#650) Deterministic Time Slicing, which allows large messages to execute across multiple rounds, was being tested in advance of releasing it as system settings. Now that t[he system settings are being updated](dfinity#621), we no longer need special configuration to test this on system subnets.
…finity#621) This is a follow-up change to further decrease the DTS slice limit on system subnets for regular messages. The value is set to 2B instructions to match the setting on application subnets. `install_code` messages still use the bigger slice limit until the checkpoint interval is adjusted and we can afford reducing that as well. This will change in a future PR.
Disable DTS in `drun` for system subnets to enable deterministic debug output testing. **Background information**: DTS aborts uncompleted messsages if they reach a checkpoint and retries them later. However, debug prints of such DTS-aborted executions leak, which leads to non-deterministic debug outputs and can disturb testing with `drun`. Therefore, disable DTS on system subnets in `drun` for deterministic debug outputs as required by Motoko's tests. This testing issue has become noticeable with dfinity#621.
This is a follow-up change to further decrease the DTS slice limit on system subnets for regular messages. The value is set to 2B instructions to match the setting on application subnets.
install_code
messages still use the bigger slice limit until the checkpoint interval is adjusted and we can afford reducing that as well. This will change in a future PR.