-
-
Notifications
You must be signed in to change notification settings - Fork 200
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
get.adjlist very very slow, and potential fix #194
Comments
Thanks! Would you like to submit a pull request? |
Sure thing. Do you prefer the first or second version, the second has a precedent in rigraph/R/structural.properties.R Line 1702 in 665d71e
|
Second is good. But we should probably add a class. G
On 25 May 2017 07:12, "Chris Hammill" <notifications@github.com> wrote:
Sure thing. Do you prefer the first or second version, the second has a
precedent in ego https://github.com/igraph/rigr
aph/blob/665d71ebd40cdfe9b996a4f50c35d65b791e4102/R/
structural.properties.R#L1702
—
You are receiving this because you commented.
Reply to this email directly, view it on GitHub
<#194 (comment)>, or mute
the thread
<https://github.com/notifications/unsubscribe-auth/AAoTQF4WXYdStIKcApCNCw8Wh-jwtyV5ks5r9Yw5gaJpZM4Nc1In>
.
|
Hmm, looking at the Setting that option to |
I think this is now basically fixed as we use the new |
For large graphs get.adjlist is very slow, for a graph with 125000 vertices, and 735000 edges
The C-code to extract the neighbours isn't the culprit
The slowness can be traced to:
I suspect the proper vertex list indexing is overkill here and causing an extreme slowdown. Since the return-type from c-code should be guaranteed to be a list of integer vectors, and the doc promises to return a list of integer vectors could we get away with:
Or potentially even:
Benchmarks:
The text was updated successfully, but these errors were encountered: