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

fix: update benchmark command #1631

Merged
merged 4 commits into from
Jul 10, 2023
Merged

fix: update benchmark command #1631

merged 4 commits into from
Jul 10, 2023

Conversation

mattheworris
Copy link
Collaborator

@mattheworris mattheworris commented Jul 7, 2023

Goal

The goal of this PR is to update the benchmark command with an additional argument --additional-trie-layers=20.

Closes #1630

Discussion

Due to changes in Polkadot v0.9.38, it is recommended to update the benchmark command.

Checklist

  • Chain spec updated
  • Custom RPC OR Runtime API added/changed? Updated js/api-augment.
  • Design doc(s) updated
  • Tests added
  • Benchmarks added
  • Weights updated

@mattheworris mattheworris linked an issue Jul 7, 2023 that may be closed by this pull request
@mattheworris mattheworris marked this pull request as ready for review July 7, 2023 15:55
@github-actions
Copy link

github-actions bot commented Jul 7, 2023

Running benchmarks and calculating weights. DO NOT MERGE! A new commit will be added upon completion...

@enddynayn
Copy link
Collaborator

enddynayn commented Jul 7, 2023

additional reference: paritytech/substrate#11637

@github-actions
Copy link

github-actions bot commented Jul 7, 2023

Finished running benchmarks. Updated weights have been committed to this PR branch in commit 2907038.

@github-actions github-actions bot added the metadata-changed Metadata has changed since the latest full release label Jul 7, 2023
@mattheworris mattheworris requested a review from a team July 7, 2023 19:29
@github-actions github-actions bot added metadata-changed Metadata has changed since the latest full release and removed metadata-changed Metadata has changed since the latest full release labels Jul 7, 2023
Copy link
Collaborator

@JoeCap08055 JoeCap08055 left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Do we need to update the spec_version just because weights were updated? Otherwise lgtm.

@mattheworris mattheworris merged commit bd6433a into main Jul 10, 2023
@mattheworris mattheworris deleted the 1630-pov-benchmarking branch July 10, 2023 13:56
@mattheworris
Copy link
Collaborator Author

Yes, after the weights were updated, the metadata-mismatch test triggered.

shannonwells pushed a commit that referenced this pull request Apr 16, 2024
# Goal
The goal of this PR is to update the benchmark command with an
additional argument `--additional-trie-layers=20`.

Closes #1630 

# Discussion
Due to changes in Polkadot v0.9.38, it is recommended to update the
benchmark command.

# Checklist
- [x] Chain spec updated
- [ ] Custom RPC OR Runtime API added/changed? Updated js/api-augment.
- [ ] Design doc(s) updated
- [ ] Tests added
- [ ] Benchmarks added
- [x] Weights updated

---------

Co-authored-by: Frequency CI [bot] <do-not-reply@users.noreply.github.com>
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
metadata-changed Metadata has changed since the latest full release
Projects
None yet
Development

Successfully merging this pull request may close these issues.

PoV benchmarking
4 participants