-
Notifications
You must be signed in to change notification settings - Fork 11
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
Replace one update call per row with one update call for multiple rows #1518
Replace one update call per row with one update call for multiple rows #1518
Conversation
…-large-update-per-table
…-large-update-per-table
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 1 of 4 files at r1, 3 of 3 files at r2, all commit messages.
Reviewable status: complete! all files reviewed, all discussions resolved (waiting on @tristanvuong2021)
…-large-update-per-table
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 1 of 4 files at r1, 3 of 3 files at r2, all commit messages.
Reviewable status: complete! all files reviewed, all discussions resolved (waiting on @tristanvuong2021)
…-large-update-per-table
The addBinding method executes one update per row. When the number of rows is large, the performance suffers. For 800 measurements, update takes 1.4 seconds locally. With the change in this PR, update takes 0.8 seconds.
The refactoring is done this way because R2DBC doesn't automically transform the update into a single batch update. See pgjdbc/r2dbc-postgresql#527.