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

Performance issue with keys() requests in Chrome #1072

Open
fxi opened this issue Nov 24, 2022 · 0 comments
Open

Performance issue with keys() requests in Chrome #1072

fxi opened this issue Nov 24, 2022 · 0 comments

Comments

@fxi
Copy link

fxi commented Nov 24, 2022

Hi there.

I just got a weird issue. Not reproducible... sorry.

For an unknown reason, .keys() and .iterate became very slow in my app.
I wrote a script that mimics what's happening :
https://jsfiddle.net/fxi/hg07voey/1/
There, .keys() is fast. Same browser. Different results.

What could make .keys() being slow in another context ?


Here are timing from my app, to get keys from ~200 items of 250b.

  ms
chrome 4440.856
chrome incognito 43.587
firefox 18

Versions :

  • Browser : Chrome 107.0.5304.110 (Official Build) (arm64)
  • localforage : 1.10.0

I tried :

  • Removing the DB
  • Removing All DB
  • Removing application cache ( clear site data )
  • Rebooting ( you know... )

Observations :

  • I don't have any extension.
  • In the performance profile, I've seen that nothing is happening during those 4400ms, except loads of events from localforage ( 0ms blocking)...
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

No branches or pull requests

1 participant