Skip to content
This repository was archived by the owner on Apr 12, 2024. It is now read-only.

perf($scope): Add a property $$watchersCount to scope #5799

Closed
wants to merge 1 commit into from

Conversation

lgalfaso
Copy link
Contributor

Add a property $$watchersCount to scope that keeps the number of watchers in the scope plus all the child scopes. Use this property when traversing scopes looking for watches

@lgalfaso
Copy link
Contributor Author

rebase and added a few benchmarks

@IgorMinar
Copy link
Contributor

This looks interesting. @lgalfaso, is it still relevant?

@lgalfaso
Copy link
Contributor Author

@IgorMinar it does make a difference when there are a lot of bind-once expressions. Will rebase it on top of trunk

@lgalfaso
Copy link
Contributor Author

rebase on top of master

@IgorMinar
Copy link
Contributor

Do we have a benchmark that shows the impact?
On Oct 31, 2014 9:08 AM, "Lucas Galfasó" [email protected] wrote:

rebase on top of master


Reply to this email directly or view it on GitHub
#5799 (comment).

@lgalfaso
Copy link
Contributor Author

lgalfaso commented Nov 5, 2014

@IgorMinar the new test and the existing bind-once test show a big performance boost. That said, the test is is synthetic so the real world performance improvements will be a lot smaller

Add a property $$watchersCount to scope that keeps the number of
watchers in the scope plus all the child scopes. Use this property
when traversing scopes looking for watches
@petebacondarwin
Copy link
Contributor

This looks good. I need to give it a run out first.

@lgalfaso
Copy link
Contributor Author

landed as c1500ea

@lgalfaso lgalfaso closed this Jan 30, 2015
lgalfaso added a commit that referenced this pull request Jan 30, 2015
Add a property $$watchersCount to scope that keeps the number of
watchers in the scope plus all the child scopes. Use this property
when traversing scopes looking for watches

Closes: #5799
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Projects
None yet
Development

Successfully merging this pull request may close these issues.

5 participants