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

[Bug] Performance Impact on Multiple SetItem Calls #226

Open
cswierczynski opened this issue Nov 9, 2023 · 0 comments
Open

[Bug] Performance Impact on Multiple SetItem Calls #226

cswierczynski opened this issue Nov 9, 2023 · 0 comments
Labels
Bug Something isn't working Triage Issue needs to be triaged

Comments

@cswierczynski
Copy link

Describe the bug
SetItemAsync method takes a long time to complete after multiple calls. The first time it's called, it takes less than a second to complete. On about the 4th or 5th time, it takes about a minute and a half to complete.

To Reproduce
Steps to reproduce the behavior:

  1. Call SetItemAsync once with any Key/Value
  2. Wait a few seconds
  3. Call SetItemAsync again with any Key/Value
  4. Wait a few seconds
  5. Call SetItemAsync again with any Key/Value
  6. Performance Impact should be seen by now

Expected behavior
SetItemAsync should take around the same time to execute each time it is called

Screenshots
The first screenshot below shows the time/resources it took to execute the 1st SetItemAsync, which less than 1sec
image

3rd execution: ~22sec
image

4th or 5th SetItemAsync: More than 1.5min

image

Hosting Model (is this issue happening with a certain hosting model?):

  • Blazor WebAssembly
@cswierczynski cswierczynski added Bug Something isn't working Triage Issue needs to be triaged labels Nov 9, 2023
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Bug Something isn't working Triage Issue needs to be triaged
Projects
None yet
Development

No branches or pull requests

1 participant