Skip to content

fix: update benchmark command - #1631

Merged
mattheworris merged 4 commits into
mainfrom
1630-pov-benchmarking
Jul 10, 2023
Merged

mattheworris merged 4 commits into
mainfrom
1630-pov-benchmarking

Conversation

@mattheworris

@mattheworris mattheworris commented Jul 7, 2023 •

Copy link
Copy Markdown
Collaborator

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
@mattheworris
mattheworris requested a review from wilwade as a code owner July 7, 2023 15:55
@github-actions

github-actions Bot commented Jul 7, 2023

Copy link
Copy Markdown

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

@enddynayn

enddynayn commented Jul 7, 2023 •

Copy link
Copy Markdown
Collaborator

additional reference: paritytech/substrate#11637

@github-actions

github-actions Bot commented Jul 7, 2023

Copy link
Copy Markdown

✅ 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

@JoeCap08055 JoeCap08055 left a comment

Copy link
Copy Markdown
Collaborator

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
Copy Markdown
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

5 participants