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

De-duplicate async renders #1201

Open
Archmonger opened this issue Feb 26, 2024 · 0 comments
Open

De-duplicate async renders #1201

Archmonger opened this issue Feb 26, 2024 · 0 comments
Labels
priority-1-high Should be resolved ASAP. type-revision About a change in functionality or behavior

Comments

@Archmonger
Copy link
Contributor

Archmonger commented Feb 26, 2024

Current Situation

This change now allow renders to take place concurrently. To keep things simple, no effort is made to deduplicate renders. For example, if parent and child components are scheduled to render at the same time, both scheduled renders will take place even though a single render of the parent component would be sufficient to update the view.

Proposed Actions

Attempt to de-duplicate renders. This can either occur in one of two ways

  1. Checking if a parent element is already in the render queue.
  2. Removing child elements from the render queue after a successful render.

The direction we go in will depend on which one can be written in a more performant manner.

@Archmonger Archmonger added priority-1-high Should be resolved ASAP. type-revision About a change in functionality or behavior labels Feb 26, 2024
@reactive-python reactive-python deleted a comment from dickermoshe Nov 17, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
priority-1-high Should be resolved ASAP. type-revision About a change in functionality or behavior
Projects
None yet
Development

No branches or pull requests

1 participant