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

Tune sweat.claim workload to saturate chunk capacity #11145

Open
2 tasks
Tracked by #11143
aborg-dev opened this issue Apr 24, 2024 · 2 comments
Open
2 tasks
Tracked by #11143

Tune sweat.claim workload to saturate chunk capacity #11145

aborg-dev opened this issue Apr 24, 2024 · 2 comments

Comments

@aborg-dev
Copy link
Contributor

aborg-dev commented Apr 24, 2024

In #11119 we added sweat.claim workload to Locust load-test setup.

@mooori noted that we would need to adjust the workload to make it more useful.

I suggest we tune it to:

  • Make sure we have the settings that can saturate the capacity of the chunk
  • Make the workload similar to mainnet traffic
@aborg-dev
Copy link
Contributor Author

cc #11808

@mooori
Copy link
Contributor

mooori commented Jul 19, 2024

Shortly after the Locust workload was added, sweat-claim was refactored. From what I remember off the top of my head, the current workload might not reflect well what happens in v2 of sweat-claim. This summary and the pointers it contains may be a starting point for analyzing this.

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

No branches or pull requests

2 participants