-
Notifications
You must be signed in to change notification settings - Fork 46
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
Route performance problems using updateOnRouterChange #97
Comments
I did some digging and the intercom update function is being called many times due to a subscription matching all router events. Changing this to match for NavigationEnd should fix the issue. |
2 tasks
Hi @scott-wyatt @wbhob – Are you able to publish with this change? |
@scott-wyatt, @wbhob – I hate to be that guy but what's the eta on getting 8.0.1 published to npm? |
Opps! Sorry about that, I thought it published. I’ll publish it to npm this morning
Sent from out and about
… On Jan 15, 2020, at 2:50 AM, Andy Hook ***@***.***> wrote:
Hi @scott-wyatt @wbhob – Are you able to publish with this change?
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub, or unsubscribe.
|
Thanks for getting this out! 🎉 |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Versions
Description
I'm experiencing significant performance problems when changing routes with updateOnRouterChange enabled. In my profiler some of my tasks takes up to 5 or 6 times as long.
Here's an example from clicking between two routes in my app:
updateOnRouterChange: false
updateOnRouterChange: true
Has anyone come up against these issues before?
The text was updated successfully, but these errors were encountered: