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

Betweenness Centrality Tractability? #44

Open
cookieups opened this issue Jan 6, 2016 · 2 comments
Open

Betweenness Centrality Tractability? #44

cookieups opened this issue Jan 6, 2016 · 2 comments

Comments

@cookieups
Copy link

Running this algo on a directed graph with 30K nodes and 50K Edges is extremely slow. The output during betweennessCentralityMap phase is roughly 1 vertex completed per 3 minutes. I realize that this can be a O(n^3) scale problem depending on algorithm, but this seems prohibitively slow. Running this on a single VM with 10 GB of Memory and 3 cores. Is this behavior normal?

@kbastani
Copy link
Member

kbastani commented Jan 7, 2016

I agree, this could certainly be improved. I will take a deeper look and see what I can do to improve it.

@cookieups
Copy link
Author

Other betweenness centrality programs I've seen that are somewhat efficient have implemented the Brandes "Faster" Algorithm (usually single threaded). On the same set above, it completes in roughly 3 minutes (250 Edges per second), and on a larger set (120K V, 9 MM E) roughly 5 hours (500 Edges per Second) for both Vertex Betweenness Centrality and Edge Betweenness Centrality:

http://algo.uni-konstanz.de/publications/b-fabc-01.pdf

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

No branches or pull requests

2 participants