Skip to content
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

Pending Rococo benchmarks #850

Open
3 of 5 tasks
brunopgalvao opened this issue Mar 22, 2022 · 11 comments
Open
3 of 5 tasks

Pending Rococo benchmarks #850

brunopgalvao opened this issue Mar 22, 2022 · 11 comments

Comments

@brunopgalvao
Copy link
Contributor

brunopgalvao commented Mar 22, 2022

Follow up to paritytech/polkadot#5052

Generate Rococo weights for the following:

The following weights were copied from Polkadot and need to be re-generated for Rococo

Additionally, XCM needs to be added as a benchmark for Rococo.

  • Add XCM benchmark and generate weights
@ggwpez
Copy link
Member

ggwpez commented Mar 22, 2022

Please also have a look at the comments from the first MR, since there seems to be some mixup.

@shawntabrizi
Copy link
Member

Adding XCM benchmarks is not trivial, and probably something that should be put off for later.

These last few benchmarks we can handle.

@coderobe
Copy link
Contributor

coderobe commented Apr 2, 2022

I'm going to add rococo to the existing weights benchmarking pipelines anyway which will take care of regenerating the weights

@nuke-web3
Copy link
Contributor

Checking in here, is this good to close now cc @brunopgalvao @al3mart ?

@brunopgalvao
Copy link
Contributor Author

This can be closed when this issue is closed: paritytech/polkadot#5617 as it has the XCM benchmarks in there.

@NachoPal
Copy link
Contributor

NachoPal commented Jun 24, 2022

This can be closed when this issue is closed: paritytech/polkadot#5617 as it has the XCM benchmarks in there.

We don't want pallet_session benchmarks to be a blocker of paritytech/polkadot#5617, runtime upgrade can happen with the current weights.

XCM weights will be added.

@NachoPal
Copy link
Contributor

My findings about the state of Rococo benchmarks after paritytech/polkadot#5617 is merged.

@brunopgalvao
Copy link
Contributor Author

@ggwpez anything we can do here?

@ggwpez
Copy link
Member

ggwpez commented Aug 1, 2022

Yea I think I know whats going on. Fix should be trivial, will open an MR.

@ggwpez
Copy link
Member

ggwpez commented Aug 2, 2022

Ah actually not sure anymore. I thought it was easy, but not that much anymore.
Should this not already be fixed if the Rococo runtime is the same as Kusama?
Somehow the benches still fail on the udpated-rococo-runtime MR...

@NachoPal
Copy link
Contributor

NachoPal commented Aug 2, 2022

Ah actually not sure anymore. I thought it was easy, but not that much anymore. Should this not already be fixed if the Rococo runtime is the same as Kusama? Somehow the benches still fail on the udpated-rococo-runtime MR...

We don't want to block the PR because of the benchmarks. That PR has been waiting already too long. In addition, since those benchmarks apparently never worked, it doesn't seem critical to have them fixed before the runtime upgrade.

We'd like to address them in a different PR.

@Sophia-Gold Sophia-Gold transferred this issue from paritytech/polkadot Aug 24, 2023
claravanstaden pushed a commit to Snowfork/polkadot-sdk that referenced this issue Dec 8, 2023
helin6 pushed a commit to boolnetwork/polkadot-sdk that referenced this issue Feb 5, 2024
Bumps [lru](https://github.com/jeromefroe/lru-rs) from 0.7.8 to 0.8.0.
- [Release notes](https://github.com/jeromefroe/lru-rs/releases)
- [Changelog](https://github.com/jeromefroe/lru-rs/blob/master/CHANGELOG.md)
- [Commits](jeromefroe/lru-rs@0.7.8...0.8.0)

---
updated-dependencies:
- dependency-name: lru
  dependency-type: direct:production
  update-type: version-update:semver-minor
...

Signed-off-by: dependabot[bot] <support@github.com>

Signed-off-by: dependabot[bot] <support@github.com>
Co-authored-by: dependabot[bot] <49699333+dependabot[bot]@users.noreply.github.com>
serban300 pushed a commit to serban300/polkadot-sdk that referenced this issue Mar 26, 2024
serban300 pushed a commit to serban300/polkadot-sdk that referenced this issue Mar 27, 2024
serban300 pushed a commit to serban300/polkadot-sdk that referenced this issue Apr 8, 2024
serban300 pushed a commit to serban300/polkadot-sdk that referenced this issue Apr 8, 2024
serban300 pushed a commit to serban300/polkadot-sdk that referenced this issue Apr 8, 2024
serban300 pushed a commit to serban300/polkadot-sdk that referenced this issue Apr 8, 2024
serban300 pushed a commit to serban300/polkadot-sdk that referenced this issue Apr 8, 2024
serban300 pushed a commit to serban300/polkadot-sdk that referenced this issue Apr 9, 2024
serban300 pushed a commit to serban300/polkadot-sdk that referenced this issue Apr 9, 2024
serban300 pushed a commit to serban300/polkadot-sdk that referenced this issue Apr 9, 2024
serban300 pushed a commit to serban300/polkadot-sdk that referenced this issue Apr 9, 2024
serban300 pushed a commit to serban300/polkadot-sdk that referenced this issue Apr 9, 2024
serban300 pushed a commit to serban300/polkadot-sdk that referenced this issue Apr 9, 2024
serban300 pushed a commit to serban300/polkadot-sdk that referenced this issue Apr 10, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

6 participants