crypto-org-chain / cronos

Cronos is the first Ethereum-compatible blockchain network built on Cosmos SDK technology. Cronos aims to massively scale the DeFi, GameFi, and overall Web3 user community by providing builders with the ability to instantly port apps and crypto assets from other chains while benefiting from low transaction fees, high throughput, and fast finality.
Other
296 stars 238 forks source link

Problem: configs are baked in testground #1561

Closed mmsqe closed 2 months ago

mmsqe commented 3 months ago

๐Ÿ‘ฎ๐Ÿป๐Ÿ‘ฎ๐Ÿป๐Ÿ‘ฎ๐Ÿป !!!! REFERENCE THE PROBLEM YOUR ARE SOLVING IN THE PR TITLE AND DESCRIBE YOUR SOLUTION HERE !!!! DO NOT FORGET !!!! ๐Ÿ‘ฎ๐Ÿป๐Ÿ‘ฎ๐Ÿป๐Ÿ‘ฎ๐Ÿป

PR Checklist:

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

Summary by CodeRabbit

Summary by CodeRabbit

coderabbitai[bot] commented 3 months ago

Walkthrough

The changes introduce a new command-line argument, --num_max_workers, across multiple files in the testground benchmark suite. This parameter allows users to specify the maximum number of worker threads for concurrent transaction processing. Modifications include updates to function signatures, internal logic adjustments, and the addition of a configuration parameter in the local.toml file, enhancing the configurability and scalability of the benchmarking process.

Changes

File Path Change Summary
testground/README.md Added --num_max_workers parameter to the command for running stateless test cases.
testground/benchmark/benchmark/main.py Modified entrypoint function to include ctx.params.num_max_workers in generate_load call.
testground/benchmark/benchmark/params.py Introduced num_max_workers property method to retrieve maximum workers from test_instance_params.
testground/benchmark/benchmark/sendtx.py Updated generate_load function to accept num_max_workers, replacing hardcoded num_accounts.
testground/benchmark/benchmark/stateless.py Added num_max_workers parameter to gen and patch_configs_local functions.
testground/benchmark/benchmark/peer.py Modified patch_configs function to include config_patch and app_patch parameters.
testground/benchmark/compositions/local.toml Introduced num_max_workers configuration parameter set to "3000".

Sequence Diagram(s)

sequenceDiagram
    participant User
    participant CLI
    participant Main
    participant LoadGenerator
    participant Params

    User->>CLI: Run command with --num_max_workers
    CLI->>Main: Pass num_max_workers
    Main->>Params: Retrieve num_max_workers
    Main->>LoadGenerator: Call generate_load with num_max_workers
    LoadGenerator->>LoadGenerator: Execute load generation with specified workers

๐Ÿ‡ "In the meadow, I hop and play,
New threads join the fray today!
With workers plenty, weโ€™ll send with glee,
Transactions flying, oh what a spree!
Configured well, we dance and cheer,
In our benchmark world, weโ€™ve nothing to fear!" ๐Ÿ‡

Possibly related PRs


Recent review details **Configuration used: CodeRabbit UI** **Review profile: CHILL**
Commits Files that changed from the base of the PR and between ac32495182e67a1c12cedacffadc695f2ba70869 and 013d2f51b9163781415b81e0844130e64f11b160.
Files selected for processing (1) * testground/benchmark/benchmark/stateless.py (4 hunks)
Additional context used
Ruff
testground/benchmark/benchmark/stateless.py
50-50: Do not use mutable data structures for argument defaults Replace with `None`; initialize within function (B006) --- 51-51: Do not use mutable data structures for argument defaults Replace with `None`; initialize within function (B006)
Additional comments not posted (4)
testground/benchmark/benchmark/stateless.py (4)
`76-76`: **LGTM!** The changes to the `patch_configs_local` function call, passing the `config_patch` and `app_patch` arguments, are consistent with the updated function signature. --- `85-86`: **LGTM!** The changes to the `patch_configs_local` function call, passing the `config_patch` and `app_patch` arguments, are consistent with the updated function signature. --- `276-277`: **LGTM!** The changes to the `patch_configs_local` function signature, adding the `config_patch` and `app_patch` parameters, enhance the configurability of the function and align with the AI-generated summary. --- `282-282`: **LGTM!** The changes to the `patch_configs` function call, passing the `config_patch` and `app_patch` arguments, are consistent with the overall theme of enhancing configurability.
--- 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 .` - `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 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](https://discord.com/invite/GsXnASn26c) to get help, request features, and share feedback. - Follow us on [X/Twitter](https://twitter.com/coderabbitai) for updates and announcements.
codecov[bot] commented 3 months ago

Codecov Report

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

Project coverage is 15.24%. Comparing base (7b402ef) to head (013d2f5). Report is 1 commits behind head on main.

:exclamation: There is a different number of reports uploaded between BASE (7b402ef) and HEAD (013d2f5). Click for more details.

HEAD has 12 uploads less than BASE | Flag | BASE (7b402ef) | HEAD (013d2f5) | |------|------|------| ||2|0| |integration_tests|20|10|
Additional details and impacted files [![Impacted file tree graph](https://app.codecov.io/gh/crypto-org-chain/cronos/pull/1561/graphs/tree.svg?width=650&height=150&src=pr&token=92w0Dz1Coj&utm_medium=referral&utm_source=github&utm_content=comment&utm_campaign=pr+comments&utm_term=crypto-org-chain)](https://app.codecov.io/gh/crypto-org-chain/cronos/pull/1561?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 #1561 +/- ## =========================================== - Coverage 36.12% 15.24% -20.89% =========================================== Files 97 67 -30 Lines 7725 4874 -2851 =========================================== - Hits 2791 743 -2048 + Misses 4585 4037 -548 + Partials 349 94 -255 ``` [see 47 files with indirect coverage changes](https://app.codecov.io/gh/crypto-org-chain/cronos/pull/1561/indirect-changes?src=pr&el=tree-more&utm_medium=referral&utm_source=github&utm_content=comment&utm_campaign=pr+comments&utm_term=crypto-org-chain)
yihuang commented 3 months ago

3 7 testplan-{index} 200 15 3000

what is the meaning of the fields?

mmsqe commented 3 months ago

3000

validator_count:   3
fullnode_count:    7
num_accounts:      200
num_txs:           15
num_max_workers:   3000
yihuang commented 3 months ago

3000

validator_count:   3
fullnode_count:    7
num_accounts:      200
num_txs:           15
num_max_workers:   3000

what's the point of setting thread pool size larger than accounts, there's only one task for each account.