Re-adding SqlUpdatesWithProcedures (with build fixes) #40
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.
Same as #37 but with fixes for the build (previous pull request was missing the latest commit from master, and so there was a build error around
apps/SqlUpdatesWithProcedures.java:[69,3] method does not override or implement a method from a supertype
).Old PR message from #37:
As mentioned in the comments of #37,
SqlUpdatesWithProcedures
differs fromSqlUpdates
in that this workload will only sendnum_writes
unique updates (the uniqueness is to avoid transaction conflicts). Thus this workload can also be used for performance timing, as it will exit after it has finished all its updates.Typical use case of this workload is via first running SqlInserts:
Then by running SqlUpdatesWithProcedures:
A few things to note:
update_batch_size
is 50 since postgres only allows procedures to have at most 100 parameters, and we are currently just passing in key/value pairs to be updated (100/2 = 50).\c postgres
andcreate table postgresqlkeyvalue(k text primary key, v text) split into 1 tablets;
in ysqlsh prior to runningSqlUpdates