-
-
Notifications
You must be signed in to change notification settings - Fork 1.5k
Component lifecycle scheduler optimizations #2065
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
Conversation
|
@intendednull 👋 RE: #1946 I wonder whether you could point your project to this change and see if the issue still persists? I've had a sneaking feeling that it might be due to the scheduler and some of the changes of priority here could possible prevent the issue. I don't have a way to replicate the issue on For me the PR isn't blocked on whether #1946 is fixed, but rather it would be nice to know if this has provided the fix so that the issue can be linked and @bakape can receive a well earned reward 🎉 |
|
If I understand the issued correctly, me moving the |
|
As a side note, the gains in benchmarks are not really from render deduplication but other lifecycle and scheduler optimizations. The former only comes into play with more complex graph-like update flows. |
|
No luck, issue is present here as well. @mc1098 I think you're right about it being related to the scheduler. At the bottom of this stack trace we see the scheduler is running because an agent message was added ( Am becoming more convinced my issue is a little different than originally posted in #1946. |
Shame :) but thank you so much @intendednull for trying ❤️
That was my thinking, we probably should include some logging/tracing in debug so that we can actually see what lifecycle events are happening and when. This would be a different PR ofc.
I'm not sure tbh 🙃 |
mc1098
left a comment
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Looks good to me :)
I appreciate all the comments, especially for each step in fill_queue 👍
|
logging/tracing in debug so that we can actually see what lifecycle
events are happening and when
Already on it. No shame in adding it to this PR.
…On Tue, 21 Sept 2021 at 10:29, mc1098 ***@***.***> wrote:
***@***.**** approved this pull request.
Looks good to me :)
I appreciate all the comments, especially for each step in fill_queue 👍
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub
<#2065 (review)>,
or unsubscribe
<https://github.com/notifications/unsubscribe-auth/AB347MDDWFQ4NX5BBMBMTRTUDAX6LANCNFSM5EKL4M6Q>
.
Triage notifications on the go with GitHub Mobile for iOS
<https://apps.apple.com/app/apple-store/id1477376905?ct=notification-email&mt=8&pt=524675>
or Android
<https://play.google.com/store/apps/details?id=com.github.android&referrer=utm_campaign%3Dnotification-email%26utm_medium%3Demail%26utm_source%3Dgithub>.
|
Pull request has been modified.
|
@intendednull Try now! Panic message should be more helpful. Make sure to build it in debug mode! |
|
@bakape okay ya! now I'm getting |
|
Okay, now we know it's not an early deletion but a legit lack of mounting.
…On Tue, 21 Sep 2021, 21:23 Noah Corona, ***@***.***> wrote:
@bakape <https://github.com/bakape> okay ya! now I'm getting panicked at
'no node_ref; VComp should be mounted after: []
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub
<#2065 (comment)>, or
unsubscribe
<https://github.com/notifications/unsubscribe-auth/AB347MEZBPPFGWJ3LHGX2OTUDDERNANCNFSM5EKL4M6Q>
.
Triage notifications on the go with GitHub Mobile for iOS
<https://apps.apple.com/app/apple-store/id1477376905?ct=notification-email&mt=8&pt=524675>
or Android
<https://play.google.com/store/apps/details?id=com.github.android&referrer=utm_campaign%3Dnotification-email%26utm_medium%3Demail%26utm_source%3Dgithub>.
|
mc1098
left a comment
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Looks good to me 🎉
Thanks for adding event logging ❤️
Pull request has been modified.
Description
render()andrendered()calls.view()calls - they have been moved to the render lifecycle event.ComponentStatememory footprint.Benchmark results:

Checklist
cargo make pr-flow