-
Notifications
You must be signed in to change notification settings - Fork 3k
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
[HOLD for payment 2023-09-06] Use idb-keyval in Onyx #25566
Comments
Triggered auto assignment to @maddylewis ( |
Triggered auto assignment to Design team member for new feature review - @dannymcclain ( |
No design changes required |
👋 |
This does not have to be Daily I believe. |
If you are the assigned CME please investigate whether the linked PR caused a regression and leave a comment with the results. If a regression has occurred and you are the assigned CM follow the instructions here. If this regression could have been avoided please consider also proposing a recommendation to the PR checklist so that we can avoid it in the future. |
|
The solution for this issue has been 🚀 deployed to production 🚀 in version 1.3.58-5 and is now subject to a 7-day regression period 📆. Here is the list of pull requests that resolve this issue: If no regressions arise, payment will be issued on 2023-09-06. 🎊 After the hold period is over and BZ checklist items are completed, please complete any of the applicable payments for this issue, and check them off once done.
For reference, here are some details about the assignees on this issue:
As a reminder, here are the bonuses/penalties that should be applied for any External issue:
|
just confirming that the only payment due for this one is to @hannojg, correct? is it the standard $500? |
@maddylewis I reviewed PR and I am the only one due upwork payment. I think this applies to $1000 as PR was reviewed and merged before announcement. |
agreed with @situchan |
ok got it. thanks for clarifying. let me get that payment processed rn! |
offer sent |
paid! |
Problem
While investigating performance issues on large accounts we found an issue where storing large amounts of data in onyx takes a very long time (E.g. merging the data from a OpenApp command).
Largely this was due to the underlying storage provider opening a new database transaction for every operation in a multiMerge/multiSet operation.
Solution
The idb-keyval package optimises this, as it can handle multiple operations in one database transaction.
The good thing is, that idb-keyval also uses indexedDB as storage provider, so no migration is needed.
The text was updated successfully, but these errors were encountered: