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

test(x/interchainstaking/types): add BenchamrkIntentsFromString + minor perf #1637

Conversation

odeke-em
Copy link
Contributor

Following up with PR #896 from performance advisory #804, this change brings in the benchmark and also adds a minor performance improvement to further hoist into a global the cosmos-sdk.Dec value of 1, and also pre-allocate using a size hint.

Updates #804

…or perf

Following up with PR quicksilver-zone#896 from performance advisory quicksilver-zone#804,
this change brings in the benchmark and also adds a minor
performance improvement to further hoist into a global
the cosmos-sdk.Dec value of 1, and also pre-allocate using a size hint.

Updates quicksilver-zone#804
Copy link

vercel bot commented May 29, 2024

@odeke-em is attempting to deploy a commit to the quicksilver Team on Vercel.

A member of the Team first needs to authorize it.

Copy link
Contributor

coderabbitai bot commented May 29, 2024

Walkthrough

The updates introduce benchmark tests for the IntentsFromString and SetForValoper functions in the interchainstaking module. Additionally, optimizations in the IntentsFromString function improve performance by initializing variables more efficiently and refining comparison logic.

Changes

File Change Summary
x/interchainstaking/types/bench_test.go Added benchmark tests for IntentsFromString and SetForValoper functions.
x/interchainstaking/types/msgs.go Optimized IntentsFromString by preallocating capacity and refining comparison logic.

Poem

In code's vast realm, new benchmarks rise,
To measure speed and optimize,
With IntentsFromString, swift and bright,
And SetForValoper, taking flight.
Performance gains, our goal in sight,
Interchainstaking's future, shining light.
🌟🐇✨


Tip

Early Access Features
  • gpt-4o model for chat

Thank you for using CodeRabbit. We offer it for free to the OSS community and would appreciate your support in helping us grow. If you find it useful, would you consider giving us a shout-out on your favorite social media?

Share
Tips

Chat

There are 3 ways to chat with CodeRabbit:

  • Review comments: Directly reply to a review comment made by CodeRabbit. Example:
    • I pushed a fix in commit <commit_id>.
    • Generate unit testing code for this file.
    • Open a follow-up GitHub issue for this discussion.
  • Files and specific lines of code (under the "Files changed" tab): Tag @coderabbitai in a new review comment at the desired location with your query. Examples:
    • @coderabbitai generate unit testing code for this file.
    • @coderabbitai modularize this function.
  • PR comments: Tag @coderabbitai in a new PR comment to ask questions about the PR branch. For the best results, please provide a very specific query, as very limited context is provided in this mode. Examples:
    • @coderabbitai generate interesting stats about this repository and render them as a table.
    • @coderabbitai show all the console.log statements in this repository.
    • @coderabbitai read src/utils.ts and generate unit testing code.
    • @coderabbitai read the files in the src/scheduler package and generate a class diagram using mermaid and a README in the markdown format.
    • @coderabbitai help me debug CodeRabbit configuration file.

Note: Be mindful of the bot's finite context window. It's strongly recommended to break down tasks such as reading entire modules into smaller chunks. For a focused discussion, use review comments to chat about specific files and their changes, instead of using the PR comments.

CodeRabbit Commands (invoked as PR comments)

  • @coderabbitai pause to pause the reviews on a PR.
  • @coderabbitai resume to resume the paused reviews.
  • @coderabbitai review to trigger an incremental review. This is useful when automatic reviews are disabled for the repository.
  • @coderabbitai full review to do a full review from scratch and review all the files again.
  • @coderabbitai summary to regenerate the summary of the PR.
  • @coderabbitai resolve resolve all the CodeRabbit review comments.
  • @coderabbitai configuration to show the current CodeRabbit configuration for the repository.
  • @coderabbitai help to get help.

Additionally, you can add @coderabbitai ignore anywhere in the PR description to prevent this PR from being reviewed.

CodeRabbit Configration File (.coderabbit.yaml)

  • You can programmatically configure CodeRabbit by adding a .coderabbit.yaml file to the root of your repository.
  • Please see the configuration documentation for more information.
  • If your editor has YAML language server enabled, you can add the path at the top of this file to enable auto-completion and validation: # yaml-language-server: $schema=https://coderabbit.ai/integrations/schema.v2.json

Documentation and Community

  • Visit our Documentation for detailed information on how to use CodeRabbit.
  • Join our Discord Community to get help, request features, and share feedback.
  • Follow us on X/Twitter for updates and announcements.

Copy link
Contributor

@coderabbitai coderabbitai bot left a comment

Choose a reason for hiding this comment

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

Actionable comments posted: 0

Review Details

Configuration used: CodeRabbit UI
Review profile: CHILL

Commits Files that changed from the base of the PR and between 0d4322f and 852c791.
Files selected for processing (2)
  • x/interchainstaking/types/bench_test.go (1 hunks)
  • x/interchainstaking/types/msgs.go (2 hunks)
Additional comments not posted (3)
x/interchainstaking/types/bench_test.go (2)

16-53: The benchmark setup for IntentsFromString is correctly implemented and should provide reliable performance metrics.


55-117: The benchmark setup for SetForValoper is well-constructed, testing both typical and edge cases effectively.

x/interchainstaking/types/msgs.go (1)

Line range hint 170-194: The optimizations in IntentsFromString function, including pre-allocation and the use of a precomputed oneDec variable, are well-implemented and should improve performance.

Also applies to: 201-201

Copy link

codecov bot commented May 30, 2024

Codecov Report

All modified and coverable lines are covered by tests ✅

Project coverage is 63.72%. Comparing base (0d4322f) to head (852c791).
Report is 20 commits behind head on main.

Additional details and impacted files

Impacted file tree graph

@@           Coverage Diff           @@
##             main    #1637   +/-   ##
=======================================
  Coverage   63.72%   63.72%           
=======================================
  Files         194      194           
  Lines       13740    13740           
=======================================
  Hits         8756     8756           
  Misses       4130     4130           
  Partials      854      854           
Flag Coverage Δ
unittests 63.72% <100.00%> (ø)

Flags with carried forward coverage won't be shown. Click here to find out more.

Files Coverage Δ
x/interchainstaking/types/msgs.go 86.18% <100.00%> (ø)

Copy link
Contributor

@tuantran1702 tuantran1702 left a comment

Choose a reason for hiding this comment

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

lgtm

@joe-bowman
Copy link
Contributor

Can you lint this @odeke-em so we can merge it please?

@joe-bowman
Copy link
Contributor

This pull request has been automatically marked as stale because it has not had any recent activity. It will be closed if no further activity occurs. Thank you!

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Projects
None yet
Development

Successfully merging this pull request may close these issues.

3 participants