Increase MaxMemoryPages to 512MB
PVF execution currently has a memory limit of 128MB, which is the same as Cumulus uses for its block import pipeline. While collators execute state transitions by reading parachain data from disk locally, parachain validators must load state proofs into memory. Therefore, they should have a higher memory limit than collators. Otherwise, a parachain block that made full use of memory when executed by the collator could fail to be executed by validators. To fix this, we propose increasing the memory limit for PVF execution to 512MB.
Please note that a similar proposal has already been successfully executed in Kusama. As this proposal was submitted on the Whitelisted Caller track, Fellowship will be voting on a proposal to whitelist this hash.
set_config_with_executor_params {}: set_executor_params(RawOrigin::Root, ExecutorParams::from(&[ExecutorParam::MaxMemoryPages(8192)][..]))
Call data: 0x332e040100200000
Call hash: 0x1c356149b664ec3f7d89eeb56a3469bd5f468ae7fafa2b13f2423618db6c922e
Comments (2)
Proposal Passed
3
of 3Summary
0%
Aye
0%
Nay
Aye (146)0.0 DOT
Support0.0 DOT
Nay (2)0.0 DOT
Voting Data
Approval%
Support%
Threshold0.00%
Threshold0.00%
FYI, as posted in the Polkadot Direction chat by Otar:
Similar to the proposal on Kusama, this referendum aims to increase MaxMemoryPages to 512MB: PVF execution currently has a memory limit of 128MB, which is the same as Cumulus uses for its block import pipeline. While collators execute state transitions by reading parachain data from disk locally, parachain validators must load state proofs into memory. Therefore, they should have a higher memory limit than collators. Otherwise, a parachain block that made full use of memory when executed by the collator could fail to be executed by validators. To fix this, we propose increasing the memory limit for PVF execution to 512MB.
ChaosDAO would like to provide the following feedback from our community. We offer this feedback voluntarily in the spirit of OpenGov, in order to help teams improve their proposals so we can all build the network together.
ChaosDAO votes as a collective based on the results of our anonymous internal voting procedures. Our members are not required provide any feedback as to why they have voted in a particular direction. Similarly, to respect our members' right to anonymity, we will not be sharing names of individuals who have chosen to voluntarily provide feedback.