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

Fix row-thread mapping for sequential workloads #153

Merged
merged 1 commit into from
Nov 5, 2024

Conversation

vponomaryov
Copy link
Contributor

Before this change scylla-bench was distributing rows among threads correctly only when number of partitions was divisible by number of threads without remainder.

A bit worse case was appearing when there was division remainder.

And the worst case was when number of threads was bigger than number of partitions. In this case last thread was handling all of the rows and all of other threads were idle.

So, fix it by spreading rows evenly among all of the threads as much as possible.

Closes: #138

Copy link
Contributor

@dkropachev dkropachev left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Small nit, rest looks good.

main.go Outdated Show resolved Hide resolved
Before this change scylla-bench was distributing rows among threads
correctly only when number of partitions was divisible by number of
threads without remainder.

A bit worse case was appearing when there was division remainder.

And the worst case was when number of threads was bigger than number
of partitions. In this case last thread was handling all of the rows
and all of other threads were idle.

So, fix it by spreading rows evenly among all of the threads
as much as possible.

Closes: scylladb#138
@vponomaryov vponomaryov force-pushed the fix-sequential-workload branch from 6d0c559 to e875ca7 Compare November 5, 2024 14:24
Copy link
Contributor

@fruch fruch left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

LGTM

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