Improve bulk IndexedDB performance #821
Merged
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Perform multiple IDB operations (get/put/delete) simultaneously rather than serially for bulk operations. Only the last request needs an `onsuccess` handler.
This was referenced Mar 2, 2021
Merged
Closed
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
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.
Perform multiple IDB operations (get/put/delete) simultaneously rather than serially for bulk operations. Only the last request needs an
onsuccesshandler. This approach is not only more performant but much more robust when applying very large (> 5000 record) updates.This approach results in modest performance gains for IndexedDB. In addition, I'm working on providing much more significant gains via a transform buffer that allows for complex updates that involve many record types and relationships to be truly batched and performed in a single IDB transaction.