cloud-tests: use a time-based calculation of load #16715
Merged
Conversation
This file contains 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
For HighThroughputTest::test_decomm_and_add we used a fixed value of 10,000 messages to warm up the test, but with 4K messages and high tiers this could result in a warmup time of < 1 second, which rounded to zero, causing the test to time out immediately (in addition to being an unsuitably small warmup even if it didn't time out). Instead, use a time-based workload calculation, i.e., use the number of messages we expect to be able to produce in a given time period: this will naturally scale with tier size as expected throughput increases. Fixes redpanda-data#16470.
|
ducktape was retried in https://buildkite.com/redpanda/redpanda/builds/45361#018de713-ded4-469b-acf4-a17df2f87f63 ducktape was retried in https://buildkite.com/redpanda/redpanda/builds/45361#018de726-f44f-4889-90fd-d534feb11f75 |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
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.
For HighThroughputTest::test_decomm_and_add we used a fixed value of 10,000 messages to warm up the test, but with 4K messages and high tiers this could result in a warmup time of < 1 second, which rounded to zero, causing the test to time out immediately (in addition to being an unsuitably small warmup even if it didn't time out).
Instead, use a time-based workload calculation, i.e., use the number of messages we expect to be able to produce in a given time period: this will naturally scale with tier size as expected throughput increases.
Fixes #16470.
Backports Required
Release Notes