-
Notifications
You must be signed in to change notification settings - Fork 928
Significantly decreased performance with persistence enabled #513
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
Comments
Hmmm this issue does not seem to follow the issue template. Make sure you provide all the required information. |
@mikelehen FYI since he was on the original issue :) |
This is on my radar to investigate but I haven't gotten a chance yet. Sorry for the delay! |
Any status on this? |
We made some significant speedups in #1055, but this hasn't made it into a release yet. |
This was released as part of the Firebase JavaScript SDK 5.3.1. |
If folks are still seeing unexpected performance issues, please open a new issue with details. Thanks! |
Originally posted by @yankedev here, but in the other issue which tracks something else. I'm experiencing the same problem with my app, which loads faster in the incognito window/with cleared cache than when data is persisted in IndexedDB.
Steps to reproduce:
Uncomment
angularFire.enablePersistence()
inapp.module.ts
and reload the page:https://stackblitz.com/edit/ionic-watdjp
Watch logs in the console.
The text was updated successfully, but these errors were encountered: