POC: Update / indexed db account ops integration#2513
Draft
gergana95 wants to merge 7 commits into
Draft
Conversation
|
Review the following changes in direct dependencies. Learn more about Socket for GitHub.
|
PetromirDev
requested changes
Jul 1, 2026
This file contains hidden or 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
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.
Issue is https://github.com/AmbireTech/ambire-app/issues/7264
In order to test properly with storage of accounOps please use a new browser instance and refer to the script mentioned here and load accountOps in your storage #2412
Testing Summary
Benchmarked Activity startup with 21,000 operations (3 accounts × 7 chains × 1,000 ops).
The implementation uses a timestamp index cursor per (account, chainId) group that stops reading after 20 finalized ops — only 525 out of 21,000 rows are touched at startup (2.5%). This replaces the previous load-all-then-trim approach.
The previous version (load all records → trim in JS) loaded startup data in ~1.0s. With cursor-based early stopping, the same 21,000-op dataset loads ~525 rows instead of 21,000 — a ~40× reduction in rows read — which should yield a proportionally faster startup in a real browser environment. The ~1.0s figure is no longer representative and should be re-benchmarked in the extension.
Overall