-
Notifications
You must be signed in to change notification settings - Fork 601
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
ducktape: Increase partition density to 3k per shard in the MPT #24710
Conversation
478891d
to
417bb75
Compare
Partial fix for https://redpandadata.atlassian.net/browse/CORE-8732. |
@@ -43,12 +43,16 @@ | |||
BIG_FETCH = 104857600 | |||
|
|||
# How much memory to assign to redpanda per partition. Redpanda will be started | |||
# with MIB_PER_PARTITION * PARTITIONS_PER_SHARD * CORE_COUNT memory | |||
DEFAULT_MIB_PER_PARTITION = 4 | |||
# with (MIB_PER_PARTITION * PARTITIONS_PER_SHARD * CORE_COUNT) / (PARTITIONS_MEMORY_ALLOCATION_PERCENT / 100) memory |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Should be / (PARTITIONS_MEMORY_ALLOCATION_PERCENT
be * / (PARTITIONS_MEMORY_ALLOCATION_PERCENT)
?
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
* / (PARTITIONS_MEMORY_ALLOCATION_PERCENT)
Do you mean * 100 / PARTITIONS_MEMORY_ALLOCATION_PERCENT
?
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Well I meant * (PARTITIONS_MEMORY_ALLOCATION_PERCENT)
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
It was just wrong though, it should be /
as I see now this is calculating from the partition memory alloc % to the amount RP should be started with.
|
||
# How many partitions we will create per shard: this is the primary scaling | ||
# factor that controls how many partitions a given cluster will get. | ||
DEFAULT_PARTITIONS_PER_SHARD = 1000 | ||
DEFAULT_PARTITIONS_PER_SHARD = 2000 |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Almost feels like we should read it from config, but anyway LGTM.
417bb75
to
14d392b
Compare
Increase partition density to 3k partitions per shard and adapt the test to use the new memory group aware config.
kgo-repeaters start to get pretty loaded at higher partition densities so the status query can take a bit longer.
14d392b
to
49e4fb0
Compare
Pushed the change to 3k partitions now given a fix is up. |
CI test resultstest results on build#60606
|
Increase the partition density in the MPT to 3k per shard and use the new memory group aware config.
Backports Required
Release Notes