Notifcation API is expensive #97849

Activity

1. jonahwilliams

   added

   c: performanceRelates to speed or footprint issues (see "perf:" labels)Relates to speed or footprint issues (see "perf:" labels)

   p: framework

   on Feb 4, 2022
2. jonahwilliams commented on Feb 14, 2022

   

   jonahwilliams

   on Feb 14, 2022

   ContributorAuthor

   More actions

   Even if we don't traverse the entire element tree, this still ends up quite expensive when scrolling. Consider the following chrome profile from devtools where we're spending ~30% CPU on notifications.

   @kenzieschmoll @goderbauer

   
3. jonahwilliams

   changed the title [-]Notifcation API will traverse entire Element tree if there are no listeners[/-] [+]Notifcation API is expensive[/+] on Feb 14, 2022
4. jonahwilliams commented on Feb 14, 2022

   

   jonahwilliams

   on Feb 14, 2022

   ContributorAuthor

   More actions

   Design doc in progress
5. danagbemava-nc

   added

   frameworkflutter/packages/flutter repository. See also f: labels.flutter/packages/flutter repository. See also f: labels.

   f: scrollingViewports, list views, slivers, etc.Viewports, list views, slivers, etc.

   and removed

   p: framework

   on Feb 22, 2022
6. goderbauer

   added

   P2Important issues not at the top of the work listImportant issues not at the top of the work list

   on Feb 23, 2022
7. jonahwilliams

   closed this as completedin #98451on Mar 1, 2022
8. github-actions commented on Mar 15, 2022

   

   github-actionsbot

   on Mar 15, 2022

   More actions

   This thread has been automatically locked since there has not been any recent activity after it was closed. If you are still experiencing a similar issue, please open a new bug, including the output of flutter doctor -v and a minimal reproduction of the issue.
9. github-actions

   locked as resolved and limited conversation to collaborators on Mar 15, 2022