feat: reduce contention when updating the contract_data_updated_at field for integrations #671
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.
Reduce contention updating the contract_data_updated_at for integrations, which is causing some responses to be slow while locks are waited for.
This is tricky to test in a unit test, especially as the database we use for our unit tests (Sqlite) doesn't support SKIP LOCKED, so I manually tested it using the following code.
In another shell, within 15 seconds:
The second script will complete immediately, without waiting for the first one to sleep its 15 seconds. The first script will update integrations 1 and 2, while the second script will attempt to update 2 and 3, but will only actually update 3.