-
Notifications
You must be signed in to change notification settings - Fork 0
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
Weird non-performant scaling of add_edge! #468
Comments
I am not very surprised by this. The new syntax does more work internally; it's the We might be able to make it faster, although it's mainly using functions from Graphs. A better solution which we discussed with @MasonProtter some time in the past is to have our own custom graph type and make searching over it more efficient. |
Thank you! Makes sense overall - for larger systems of neurons (~1k) I'll stick to the old syntax for performance then. One additional wrinkle: if you remove
will say the system is unbalanced, but if you include the |
Good catch @agchesebro , there was a duplication of a blox if the first connection is a self-connection. Fixed in #469 |
The new
add_edge!
functionality has some puzzling performance issue with large graphs. For example, constructing a system of 300 Izhikevich neurons with the old syntax:takes ~0.2 seconds for the loop my computer, while with the new syntax:
takes ~16s. This scales with graph size (e.g., 200 is about the same for the first loop, but ~5s for the second).
The text was updated successfully, but these errors were encountered: