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

Auto-update of all weights for 2025-02-21-1740149841 #7668

Merged
merged 1 commit into from
Feb 24, 2025

Conversation

paritytech-cmd-bot-polkadot-sdk[bot]
Copy link
Contributor

Auto-update of all weights for 2025-02-21-1740149841.

Subweight results:

@paritytech-cmd-bot-polkadot-sdk paritytech-cmd-bot-polkadot-sdk bot added the R0-silent Changes should not be mentioned in any release notes label Feb 22, 2025
@paritytech-cmd-bot-polkadot-sdk paritytech-cmd-bot-polkadot-sdk bot requested review from a team February 22, 2025 06:15
@ggwpez
Copy link
Member

ggwpez commented Feb 23, 2025

Screenshot 2025-02-22 at 20 36 37

WTF is going on with the remark... its component went from 490 to 14300 per byte. But this is worst case; people dont usually remark 4MiB of data I guess.

@ggwpez
Copy link
Member

ggwpez commented Feb 23, 2025

The downward enqueueing of messages also got quite heavy. We will need proper burn-in deployes of this to ensure that it does not break stuff.

@mordamax mordamax enabled auto-merge February 23, 2025 22:26
Copy link
Member

@bkchr bkchr left a comment

Choose a reason for hiding this comment

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

Let's get this merged to get a proper baseline.

@bkchr bkchr disabled auto-merge February 24, 2025 09:12
@bkchr bkchr merged commit 16ed029 into master Feb 24, 2025
258 of 269 checks passed
@bkchr bkchr deleted the update-weights-weekly-2025-02-21-1740149841 branch February 24, 2025 09:13
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
R0-silent Changes should not be mentioned in any release notes
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants