Nodes count statistic
Statistics of the number of nodes. For geonodes and for materials I think this would be useful. I think this makes sense since the more nodes, the higher the performance load (RAM). If you create many identical nodes, at some point you will notice that the node editor will start to throttle. You can find out what number of nodes is critical.
9 Comments
In what way? Performance wise its irrelevant.
One node can be waaay more computation expensive than other eg. shader to rgb, AO is very heavy, image texture medium, and math nodes are rather light. So their total number does not simply correspond to performance. Even single note can have diferrent performance based on settings (eg. Math: Power is 16 times slower than Add) and what GPU it is running. And in other cases adding more instruction does not affect performance at all.
In Geometry nodes there is timings benchmark overlay if You wanna compare performance, but for shader nodes i havens seen perfect solution for that (even Unreals style' instruction counting is flawed).
I mean its easy to make, but if You dont have any usacese for that then its probable waste of time that cound be used on something more impactful.
I think this makes sense since the more nodes, the higher the performance load (RAM). This is not about the load on video memory or CPU. If you create many identical nodes, at some point you will notice that the node editor will start to throttle. You can find out what number of nodes is critical.
It's about what the nodes are doing, not how many nodes you have.
You can bring your entire computer to a halt with about three or four nodes.
You are not listening to me :) I will repeat. The problem is not the performance of specific nodes or the load in the 3d viewport! Try to create a lot of nodes in any node editor (GeodNodesEditor/ShaderEditor/LogicNodesEditor-thats from UPBGE) and you will notice how the editor starts to slow down!
No. That does not make any sense. I've already explained why in first post.
If the feature told you that 27 nodes were present, what's your next step?
You can now compare it to someone else's node setup that does the same thing
That would only be relevant if all nodes were equal in computational expense, which they are not.
I think this makes sense since the more nodes, the higher the performance load (RAM). This is not about the load on video memory or CPU. If you create many identical nodes, at some point you will notice that the node editor will start to throttle. You can find out what number of nodes is critical.