Skip to content
This repository has been archived by the owner on Apr 9, 2024. It is now read-only.

Performance concerns #103

Open
Bronzdragon opened this issue Jul 23, 2023 · 1 comment
Open

Performance concerns #103

Bronzdragon opened this issue Jul 23, 2023 · 1 comment

Comments

@Bronzdragon
Copy link

Hey! I wanted to use this library for my project, but it seems it's not very performant at high node counts. I noticed my computer struggling at 200 (unconnected) nodes, and it basically slowing to a standstill at 400.

If it's possible to add some performance features for large graphs, that would be appreciated. Not rendering nodes that aren't on-screen would be a logical place to start. (Though with the connections running across the screen that might be difficult.

@BenJourdan
Copy link

I think the thing you're after would be some version of Blender's node groups. That "should" drastically cut down the number of nodes needing to be rendered at once for most applications and improve the user experience. Setzer did mention they were thinking about doing this at some point but that was a while ago (#49).
hQm56
(from https://blender.stackexchange.com/questions/156988/how-to-make-node-group-of-an-existing-material-into-a-new-group-in-python)

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

No branches or pull requests

2 participants