Increase MaxMemoryPages to 512MB

Whitelisted Caller
2 Comments
Executed
  • Content
  • AI Summary
Reply
Up
Share
Status
Decision14d
Confirmation10mins
Attempts
1
Tally
99.9%Aye
54.4%Threshold
0.1%Nay
Aye
483.17K KSM
Nay
458  KSM
  • 0.0%
  • 0.0%
  • 0.0%

Threshold

Support(5.29%)
710.66K KSM
Issuance
13.44M KSM
Votes
Nested
Flattened
Calls
Capital Pct.
Votes Pct.
  • Call
  • Metadata
  • Timeline6
  • Votes Bubble
Comments

PVF is executed by a polkadot validator during backing, approvals and disputes. It's possible requests from those systems come in simultaneously. I don't know how many of those requests may come in concurrently, but it depends on the configuration. If I were to guess, then I would suppose there would be at most 3-4 PVF executing at the same time. Assuming those numbers, in the pathological case those PVF manage to fill the whole available memory at approx. the same time, it would make at most 512 MiB of committed memory with the current 128 MiB limit. With the new parameters the amount of memory consumed only by PVFs jumps up to 2 GiB.

So that makes me wonder if there were any testing done for what would happen with those pathological values on the standard hardware?

Reply
Up