-
-
Notifications
You must be signed in to change notification settings - Fork 12
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
CPU/memory utilization improvements using d3.timer
#126
Conversation
…use detected native browser features for reduced and more efficient painting
@dalanmiller: great call, I was unaware that D3 has its own timer system. |
|
||
d3.timer(createNextFunction(), update_freq+200); | ||
|
||
# setInterval () -> |
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.
Should this still be commented out?
Ready for merge if no further comments |
# Bump up the score cap | ||
score_cap = score_cap + 1 | ||
|
||
if ret == false |
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.
Since this is CoffeeScript: if ret is false
👍 |
Since everything is now in |
https://github.com/mbostock/d3/wiki/Transitions#timers
Removed the
setInterval
functions fromlanding.coffee
and replaced them with the more efficient D3 timer. Anecdotal evidence on my machine seems that things are a bit better.I think this will improve #71
@danielmewes