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

[GSoC17] Performance issues #41

Closed
nemesifier opened this issue May 31, 2017 · 5 comments
Closed

[GSoC17] Performance issues #41

nemesifier opened this issue May 31, 2017 · 5 comments
Labels
enhancement
Projects
Rewrite netjsongraph.js
Milestone
[GSoC 17] Third e...

Comments

@nemesifier
Copy link
Member

Test the library with 1K and 10K nodes.

Guifi.net has 33K working nodes according to their website.

Maybe we should keep in consideration from the beginning that data may be streamed instead of loaded all in one go. Otherwise it will never scale. What do you think @geekplux?
@nemesifier nemesifier added this to the [GSoC 17] Third evaluation milestone May 31, 2017
@geekplux geekplux moved this from To Do to WIP in Rewrite netjsongraph.js Jul 31, 2017
@geekplux
Copy link
Contributor

geekplux commented Aug 1, 2017

Solution:

@geekplux
Copy link
Contributor

I think we need a new data structure.

@geekplux
Copy link
Contributor

screen shot 2017-08-21 at 18 31 51
screen shot 2017-08-21 at 18 36 20
screen shot 2017-08-21 at 18 36 49

@geekplux geekplux mentioned this issue Aug 21, 2017
Closed
@geekplux
Copy link
Contributor

looks like ForceAtlas2 is faster than d3-force

@geekplux
Copy link
Contributor

geekplux commented Aug 25, 2017 •
edited

Too many points in one graph are of no value, my five cents.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
enhancement
Projects
No open projects
Rewrite netjsongraph.js
WIP
Milestone
[GSoC 17] Third evaluation
Development

No branches or pull requests
2 participants
@nemesifier @geekplux