Problem: benchmark don't support batch tx

[yihuang]

Solution:

• add batch mode

👮🏻👮🏻👮🏻 !!!! REFERENCE THE PROBLEM YOUR ARE SOLVING IN THE PR TITLE AND DESCRIBE YOUR SOLUTION HERE !!!! DO NOT FORGET !!!! 👮🏻👮🏻👮🏻

PR Checklist:

• [ ] Have you read the CONTRIBUTING.md?
• [ ] Does your PR follow the C4 patch requirements?
• [ ] Have you rebased your work on top of the latest master?
• [ ] Have you checked your code compiles? (make)
• [ ] Have you included tests for any non-trivial functionality?
• [ ] Have you checked your code passes the unit tests? (make test)
• [ ] Have you checked your code formatting is correct? (go fmt)
• [ ] Have you checked your basic code style is fine? (golangci-lint run)
• [ ] If you added any dependencies, have you checked they do not contain any known vulnerabilities? (go list -json -m all | nancy sleuth)
• [ ] If your changes affect the client infrastructure, have you run the integration test?
• [ ] If your changes affect public APIs, does your PR follow the C4 evolution of public contracts?
• [ ] If your code changes public APIs, have you incremented the crate version numbers and documented your changes in the CHANGELOG.md?
• [ ] If you are contributing for the first time, please read the agreement in CONTRIBUTING.md now and add a comment to this pull request stating that your PR is in accordance with the Developer's Certificate of Origin.

Thank you for your code, it's appreciated! :)

Summary by CodeRabbit

Release Notes

• New Features

  • Added benchmark support for batch mode.
  • Introduced functionality for building and processing Ethereum transactions in batches.
  • Enhanced command-line interface with a new --batch-size option for transaction generation.
  • Added functions to retrieve block information from both Cosmos and Ethereum blockchains.

• Improvements

  • Streamlined handling of default denominations for balances.
  • Enhanced transaction sending capabilities for both Cosmos and Ethereum blockchains.
  • Improved transaction generation in parallel and retry mechanisms for load generators.

• Bug Fixes

  • Resolved issues with running single validator benchmarks and improved node shutdown processes.

[coderabbitai[bot]]

Walkthrough

The pull request introduces several enhancements across multiple files in the testground/benchmark/benchmark directory. Key changes include the addition of batch processing for transactions, updates to the command-line interface for generating transactions, new functions for retrieving block information from different blockchain sources, and modifications to linting configurations. The CHANGELOG.md has been updated to reflect these changes, including bug fixes and improvements related to transaction handling and benchmarking.

Changes

File Path	Change Summary
CHANGELOG.md	Updated with new entries for bug fixes and improvements; added benchmark support feature linked to PR #1650.
testground/benchmark/.flake8	New configuration section added for flake8, including settings for line length, ignored errors, and exclusions.
testground/benchmark/benchmark/stateless.py	Added --batch-size option for transaction generation; renamed validator-generate-load to validator_generate_load.
testground/benchmark/benchmark/stats.py	Added functions get_block_info_cosmos and get_block_info_eth; modified dump_block_stats to support multiple blockchains.
testground/benchmark/benchmark/transaction.py	Added batch processing support in transaction generation and sending; updated method signatures to include batch parameters.
testground/benchmark/benchmark/utils.py	Added DEFAULT_DENOM constant; introduced block_eth and split_batch functions.
testground/benchmark/overlay.nix	Added new build systems flake8-black and flake8-isort to the Nix expression.
testground/benchmark/pyproject.toml	Added new development dependencies for black, flake8, flake8-black, and flake8-isort.

Possibly related PRs

• #1431: Integrates Testground to perform network benchmarking, related to the improvements in benchmark support mentioned in this PR.
• #1495: Addresses performance issues in Testground test cases, which may relate to improvements in generating test transactions in parallel.
• #1504: Simplifies the benchmark setup, relevant to enhancements in the benchmarking process noted in this PR.
• #1561: Improves configurability of the Testground framework, aligning with updates regarding benchmark support.
• #1586: Introduces TPS calculations for block statistics, connecting to overall improvements in transaction handling and benchmarking.
• #1645: Enhances transaction generation to run in parallel, directly relating to improvements in generating test transactions.
• #1647: Addresses the issue of the node not shutting down by signal, complementing overall system improvements.
• #1649: Focuses on enabling the single validator benchmark to run natively, relevant to enhancements in benchmarking capabilities.
• #1651: Discusses improvements to transaction broadcasting efficiency, relating to overall performance enhancements.

Suggested reviewers

• JayT106
• mmsqe
• leejw51crypto

🐇 In the meadow, we hop and play,
New features bloom, bright as day.
Batching transactions, swift and neat,
With each change, our work's a treat!
So let’s celebrate, with joy and cheer,
For improvements made, we hold so dear! 🌼

---

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

- [X](https://twitter.com/intent/tweet?text=I%20just%20used%20%40coderabbitai%20for%20my%20code%20review%2C%20and%20it%27s%20fantastic%21%20It%27s%20free%20for%20OSS%20and%20offers%20a%20free%20trial%20for%20the%20proprietary%20code.%20Check%20it%20out%3A&url=https%3A//coderabbit.ai) - [Mastodon](https://mastodon.social/share?text=I%20just%20used%20%40coderabbitai%20for%20my%20code%20review%2C%20and%20it%27s%20fantastic%21%20It%27s%20free%20for%20OSS%20and%20offers%20a%20free%20trial%20for%20the%20proprietary%20code.%20Check%20it%20out%3A%20https%3A%2F%2Fcoderabbit.ai) - [Reddit](https://www.reddit.com/submit?title=Great%20tool%20for%20code%20review%20-%20CodeRabbit&text=I%20just%20used%20CodeRabbit%20for%20my%20code%20review%2C%20and%20it%27s%20fantastic%21%20It%27s%20free%20for%20OSS%20and%20offers%20a%20free%20trial%20for%20proprietary%20code.%20Check%20it%20out%3A%20https%3A//coderabbit.ai) - [LinkedIn](https://www.linkedin.com/sharing/share-offsite/?url=https%3A%2F%2Fcoderabbit.ai&mini=true&title=Great%20tool%20for%20code%20review%20-%20CodeRabbit&summary=I%20just%20used%20CodeRabbit%20for%20my%20code%20review%2C%20and%20it%27s%20fantastic%21%20It%27s%20free%20for%20OSS%20and%20offers%20a%20free%20trial%20for%20proprietary%20code)

🪧 Tips

### Chat There are 3 ways to chat with [CodeRabbit](https://coderabbit.ai): - Review comments: Directly reply to a review comment made by CodeRabbit. Example: - `I pushed a fix in commit , please review it.` - `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 gather interesting stats about this repository and render them as a table. Additionally, render a pie chart showing the language distribution in the codebase.` - `@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 using 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. ### Other keywords and placeholders - Add `@coderabbitai ignore` anywhere in the PR description to prevent this PR from being reviewed. - Add `@coderabbitai summary` to generate the high-level summary at a specific location in the PR description. - Add `@coderabbitai` anywhere in the PR title to generate the title automatically. ### CodeRabbit Configuration 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](https://docs.coderabbit.ai/guides/configure-coderabbit) 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](https://coderabbit.ai/docs) for detailed information on how to use CodeRabbit. - Join our [Discord Community](http://discord.gg/coderabbit) to get help, request features, and share feedback. - Follow us on [X/Twitter](https://twitter.com/coderabbitai) for updates and announcements.

[codecov[bot]]

Codecov Report

All modified and coverable lines are covered by tests :white_check_mark:

Project coverage is 16.64%. Comparing base (3303077) to head (dfb4e1f). Report is 1 commits behind head on main.

Additional details and impacted files

[](https://app.codecov.io/gh/crypto-org-chain/cronos/pull/1650?src=pr&el=tree&utm_medium=referral&utm_source=github&utm_content=comment&utm_campaign=pr+comments&utm_term=crypto-org-chain) ```diff @@ Coverage Diff @@ ## main #1650 +/- ## ======================================= Coverage 16.64% 16.64% ======================================= Files 72 72 Lines 6212 6212 ======================================= Hits 1034 1034 Misses 5055 5055 Partials 123 123 ```

[yihuang]

let's do this first: https://github.com/crypto-org-chain/cronos/pull/1651

[socket-security[bot]]

New dependencies detected. Learn more about Socket for GitHub ↗︎

Package	New capabilities	Transitives	Size	Publisher
pypi/platformdirs@4.3.6	None	0	0 B
pypi/pycodestyle@2.12.1	environment, filesystem	0	161 kB	IanLee1521, asottile

View full report↗︎