-
Notifications
You must be signed in to change notification settings - Fork 1.2k
Set PoV size limit to 10 Mb #5884
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
Changes from all commits
06108e1
0a9970a
f88331e
387f1dc
15e91e7
5452419
3095f7f
e45a650
2decfd1
c99b4b2
6fe060f
56180aa
e49907f
File filter
Filter by extension
Conversations
Jump to
Diff view
Diff view
There are no files selected for viewing
| Original file line number | Diff line number | Diff line change |
|---|---|---|
|
|
@@ -438,7 +438,7 @@ pub const MAX_HEAD_DATA_SIZE: u32 = 1 * 1024 * 1024; | |
| /// * checking updates to this stored runtime configuration do not exceed this limit | ||
| /// * when detecting a PoV decompression bomb in the client | ||
| // NOTE: This value is used in the runtime so be careful when changing it. | ||
| pub const MAX_POV_SIZE: u32 = 5 * 1024 * 1024; | ||
| pub const MAX_POV_SIZE: u32 = 10 * 1024 * 1024; | ||
|
Contributor
There was a problem hiding this comment. Choose a reason for hiding this commentThe reason will be displayed to describe this comment to others. Learn more. Did we validate this works e2e, like have a parachain that generates 10MiB PoV and confirm parachain blocks work at 6s rate with all blocks included on chain ?
Contributor
There was a problem hiding this comment. Choose a reason for hiding this commentThe reason will be displayed to describe this comment to others. Learn more. It kind of makes sense to add a glutton test with these 10MB PoVs. Later we should do a more scaled up test on Versi.
Contributor
Author
There was a problem hiding this comment. Choose a reason for hiding this commentThe reason will be displayed to describe this comment to others. Learn more. We haven't validated anything yet (beyond running local zombienets to ensure 10 Mb PoVs work in principle). The purpose of this PR is to gather opinions and concerns, we're not merging it before we do a lot of tests anyway.
Contributor
There was a problem hiding this comment. Choose a reason for hiding this commentThe reason will be displayed to describe this comment to others. Learn more.
That's what I was asking for :D.
Contributor
There was a problem hiding this comment. Choose a reason for hiding this commentThe reason will be displayed to describe this comment to others. Learn more.
But the description of the PRs and my own reasoning tells me that we can merge it. PoV should still be limited by the relay runtime config value at 5MB. To have 10MB in practice you need governance to bump the chain limit and also parachain runtimes to be adjusted.
Contributor
Author
There was a problem hiding this comment. Choose a reason for hiding this commentThe reason will be displayed to describe this comment to others. Learn more. Well, okay, I'll put that another way. By this PR, I argue that the given changeset is enough to enable 10 Mb PoVs, and I expect others to argue why it is not. @alexggh's point is that we need more testing before applying the changes, and that's fair. By now, I've finished the local tests with gluttons and will do some stress tests. After that, I'm ready to go to Versi, but I'd like to make it as close to real-life as possible on Versi, that is, to start with a regular network with 5 Mb PoVs and then upgrade it to 10 Mb step by step. But if the lack of testing is the only argument against merging it in this form, it's beautiful ;)
Contributor
There was a problem hiding this comment. Choose a reason for hiding this commentThe reason will be displayed to describe this comment to others. Learn more.
I was simply asking, because I was curious what tests we've done on this end, the fact that you ran it locally with 10MiB is good enough for me. I understand that the relay-chain configuration is guarding us against using more than 5MiB, and it is probably safe to merge it without positive evidence that the new maximum is working all the way trough our stack, I was simply trying to avoid the situation where we raise this constant because we know the relay-chain configuration is at 5MiB and it is risk free now, but then 6 months later someone else comes without this context and raises the relay-chain configuration to 10MiB because MAX_POV_SIZE is already 10MiB and it must be safe :D. |
||
|
|
||
| /// Default queue size we use for the on-demand order book. | ||
| /// | ||
|
|
||
| Original file line number | Diff line number | Diff line change |
|---|---|---|
| @@ -0,0 +1,18 @@ | ||
| title: Set PoV size limit to 10 Mb | ||
| doc: | ||
| - audience: Runtime Dev | ||
| description: |- | ||
| Bumps the default PoV size limit to 10 Mb on both relay chain and parachains. | ||
| crates: | ||
| - name: polkadot-primitives | ||
| bump: minor | ||
| - name: bridge-hub-rococo-runtime | ||
| bump: minor | ||
| - name: bridge-hub-westend-runtime | ||
| bump: minor | ||
| - name: polkadot-omni-node | ||
| bump: minor | ||
| - name: polkadot-omni-node-lib | ||
| bump: minor | ||
| - name: polkadot-parachain-bin | ||
| bump: minor |
Uh oh!
There was an error while loading. Please reload this page.