Skip to content
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

feat: Adding caching to each of the native keyvalue stores #848

Merged
merged 11 commits into from
Oct 26, 2022

Conversation

nickrandolph
Copy link
Contributor

GitHub Issue (If applicable): #847

PR Type

What kind of change does this PR introduce?

  • Feature

What is the current behavior?

Each of the native keyvalue storage providers currently read/writes directly to store, which is slow

What is the new behavior?

Reads/Writes are cached in memory (this can be configured to be disabled)

PR Checklist

Please check if your PR fulfills the following requirements:

  • Tested code with current supported SDKs
  • Docs have been added/updated which fit documentation template. (for bug fixes / features)
  • Unit Tests and/or UI Tests for the changes have been added (for bug fixes / features) (if applicable)
  • Wasm UI Tests are not showing unexpected any differences. Validate PR Screenshots Compare Test Run results.
  • Contains NO breaking changes
  • Updated the Release Notes
  • Associated with an issue (GitHub or internal)

Other information

Internal Issue (If applicable):

@nickrandolph nickrandolph force-pushed the dev/nr/keyvalueperf branch 2 times, most recently from 2438934 to efa4506 Compare October 25, 2022 08:34
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants