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

CPU/memory utilization improvements using d3.timer #126

Closed
wants to merge 4 commits into from

Conversation

dalanmiller
Copy link
Contributor

https://github.com/mbostock/d3/wiki/Transitions#timers

Removed the setInterval functions from landing.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

Daniel Alan Miller added 2 commits August 24, 2015 15:14
…use detected native browser features for reduced and more efficient painting
@mglukhovsky
Copy link
Member

@dalanmiller: great call, I was unaware that D3 has its own timer system.


d3.timer(createNextFunction(), update_freq+200);

# setInterval () ->
Copy link
Member

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?

@dalanmiller
Copy link
Contributor Author

Ready for merge if no further comments

# Bump up the score cap
score_cap = score_cap + 1

if ret == false
Copy link
Member

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

@dalanmiller
Copy link
Contributor Author

👍

@dalanmiller
Copy link
Contributor Author

Since everything is now in .es6 this will have to be rewritten.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants