FIX: Added an increase high rate load test for constant LTs#442
Open
auto-mausx wants to merge 2 commits intodevelopfrom
Open
FIX: Added an increase high rate load test for constant LTs#442auto-mausx wants to merge 2 commits intodevelopfrom
auto-mausx wants to merge 2 commits intodevelopfrom
Conversation
volovyks
reviewed
Jul 18, 2025
infra/loadtests/k6-load-test.js
Outdated
| { duration: '58m', target: 1 }, | ||
| { duration: '1m', target: 0 }, | ||
| { duration: '1m', target: 2 }, | ||
| { duration: '58m', target: 8 }, |
Contributor
There was a problem hiding this comment.
I would set it to 5 for now and see how it behaves.
Also, if we’re redefining what we consider a high load, let’s update our definitions of medium and low as well — for both constant and ramping flows.
volovyks
reviewed
Jul 18, 2025
.github/workflows/k6-ci-loadtest.yml
Outdated
| echo "lt_chain=${CHAIN:-Solana}" >> "$GITHUB_OUTPUT" | ||
| echo "lt_env=${ENV:-dev}" >> "$GITHUB_OUTPUT" | ||
| echo "lt_strategy=${STRATEGY:-constant_medium_rate_1h}" >> "$GITHUB_OUTPUT" | ||
| echo "lt_strategy=${STRATEGY:-constant_high_rate_1h}" >> "$GITHUB_OUTPUT" |
Contributor
There was a problem hiding this comment.
Isn't it too much? 8 or even 5 requests every second 24/7? I believe it will generate too many logs, CPU usage, etc. And our system can be down most of the time.
Collaborator
Author
|
@volovyks updated this to a be a bit more reasonable, kept our constant rate as our "low constant" rate, and updated med and high for more traffic. |
volovyks
approved these changes
Jul 30, 2025
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
2 participants
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
This may be a little optimistic for constant rate, 8 rps for 58 mins. We can reduce this amount if it's too crazy, but ideally we can see where we are at with a higher rate like this and adjust as needed. This may be at the upper end of the limit for RPC services, but with Alchemy we just pay for increased usage I believe.
closes #437