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.

Sign up for GitHub

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

Jump to bottom

Consider throttling dirty checking #864

Closed
PolymerCommunityBot opened this issue Nov 4, 2014 · 2 comments
Closed

Consider throttling dirty checking #864

PolymerCommunityBot opened this issue Nov 4, 2014 · 2 comments
Labels
0.5 databinding

Comments

@PolymerCommunityBot
Copy link

Issue by sorvell
Friday Aug 29, 2014 at 01:39 GMT
Originally opened as https://github.com/Polymer/polymer-dev/issues/89

Currently Polymer dirty checks explicitly via Platform.flush every time (1) a declarative event handler is fired and (2) any time async is called. Dirty checking can take long enough that it's not desireable to run it by default during high frequency events and raf loops. Polymer should throttle dirty checking such that it occurs less often in these cases. This can help address googlearchive/observe-js#68.
@PolymerCommunityBot
Copy link
Author

Comment by jmesserly
Friday Aug 29, 2014 at 02:21 GMT

agreed. closed my zones suggestion since that would cause dirty-checking to run even more often than it already does :)

@tjsavage tjsavage added the 0.5 label May 21, 2015
@sorvell sorvell removed the p1 label Jun 25, 2015
@tjsavage
Copy link
Contributor

Closing this issue due to age and the release of version 1 of Polymer - please feel free to re-open if this is incorrect.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
0.5 databinding
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
3 participants
@sorvell @tjsavage @PolymerCommunityBot