-
Notifications
You must be signed in to change notification settings - Fork 3.8k
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
workload: remove initial prefix from bank workload payload #102907
workload: remove initial prefix from bank workload payload #102907
Conversation
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.
Reviewed 2 of 2 files at r1, all commit messages.
Reviewable status: complete! 0 of 0 LGTMs obtained (waiting on @srosenberg)
7ef0474
to
ad8bd70
Compare
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 introduced about 6 years ago [1] and its purpose at the time is not clear.
Looking at that PR, I am also not sure. Maybe it was intended to be used for benchmarking? E.g., csv
workload has a microbenchmarks that relies on InitialRows
.
Reviewable status: complete! 1 of 0 LGTMs obtained (waiting on @herkolategan)
TFTRs! bors r=herkolategan,srosenberg |
bors r- |
Canceled. |
An `initial-` prefix is added to the payload column of the `bank` table when the workload is initialized. It was introduced about 6 years ago [1] and its purpose at the time is not clear. There are two main problems with it: * the `initial-` prefix suggests the payload may be updated, but that actually never happens. * as currently implemented, it assumes that the `payload-bytes` command line flag is at least `len([]byte("initial-"))`. Passing a lower value to that command line flag leads to a panic. This is an implicit assumption that should not exist. This changes the row generation function so that `payload-bytes` bytes are randomly generated and inserted into the `payload` column, without the `initial-` prefix. [1] d49d535 Epic: none Release note: None
ad8bd70
to
90a9904
Compare
I realized I quoted the wrong commit, there's a parent commit that actually introduced the bors r=herkolategan,srosenberg |
Build succeeded: |
An
initial-
prefix is added to the payload column of thebank
table when the workload is initialized. It was introduced about 6 years ago [1] and its purpose at the time is not clear. There are two main problems with it:initial-
prefix suggests the payload may be updated, but that actually never happens.payload-bytes
command line flag is at leastlen([]byte("initial-"))
. Passing a lower value to that command line flag leads to a panic. This is an implicit assumption that should not exist.This changes the row generation function so that
payload-bytes
bytes are randomly generated and inserted into thepayload
column, without theinitial-
prefix.[1] d49d535
Epic: none
Release note: None