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

iotune: allow user to set buffer size for random IO #2204

Conversation

pwrobelse
Copy link
Contributor

@pwrobelse pwrobelse commented Apr 25, 2024

In some cases the buffer size used by iotune was
incorrect. Because of that, the reported IOPS
for random write was lower than expected.

This change adds '--random-io-buffer-size '
parameter that enables users to force the buffer
size used in measurements of random read and
random write IOPS.

apps/iotune/iotune.cc Outdated Show resolved Hide resolved
@pwrobelse pwrobelse force-pushed the iotune-fix-for-incorrect-buffer-size branch from abeaa25 to 97ca725 Compare April 26, 2024 13:22
@pwrobelse pwrobelse changed the title iotune: improve usage of buffer size in random write measurements iotune: allow user to set buffer size for random IO Apr 26, 2024
apps/iotune/iotune.cc Outdated Show resolved Hide resolved
In some cases the buffer size used by iotune was
incorrect. Because of that, the reported IOPS
for random write was lower than expected.

This change adds '--random-io-buffer-size <SIZE>'
parameter that enables users to force the buffer
size used in measurements of random read and
random write IOPS.

Refs: scylladb#1698
Signed-off-by: Patryk Wrobel <patryk.wrobel@scylladb.com>
@pwrobelse pwrobelse force-pushed the iotune-fix-for-incorrect-buffer-size branch from 97ca725 to b9ff09b Compare April 30, 2024 07:47
@pwrobelse pwrobelse marked this pull request as ready for review April 30, 2024 08:18
@xemul xemul closed this in 532b795 May 23, 2024
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

Successfully merging this pull request may close these issues.

None yet

2 participants