adding an unconnected node to a graph causes slow down?

adding an unconnected node to a graph causes slow down?

Anonymous
Not applicable
1,300 Views
13 Replies
Message 1 of 14

adding an unconnected node to a graph causes slow down?

Anonymous
Not applicable

im adding nodes to my graph without connecting them up yet and each time i do this i get a big slow down.   Why is this?  if the data flow of the graph doesnt change why is it being slow?

0 Likes
1,301 Views
13 Replies
Replies (13)
Message 2 of 14

Anonymous
Not applicable

also adding a watchpoint is slow

0 Likes
Message 3 of 14

Christoph_Schaedl
Mentor
Mentor

Most important Bifrost Shortcut. 

Ctrl+  does pause the Graph.

----------------------------------------------------------------
https://linktr.ee/cg_oglu
0 Likes
Message 4 of 14

Christoph_Schaedl
Mentor
Mentor

Shortcut is Ctrl + .

https://help.autodesk.com/view/BIFROST/ENU/?guid=Bifrost_Common_build_a_graph_pause_graph_html

 

I tried to edit my post above but my slow internet messed it up.

----------------------------------------------------------------
https://linktr.ee/cg_oglu
0 Likes
Message 5 of 14

mjcg91
Collaborator
Collaborator

Not sure about it, but seems like since 2.0.5.0, adding unconnected nodes triggers the graph's recompilation.

Maxime Jeanmougin - Technical Artist
https://maximejeanmougin.com

Join the Bifrost Addicts community on Discord:
https://discord.gg/bifrost-addicts
0 Likes
Message 6 of 14

syracoj
Autodesk
Autodesk

When setting an envVar to see when the graph recompiles I am not seeing recompilation at node creation time.

But that doesn't mean there isn't a case where it is happening.

Could I have the scene file you were working with when encountering this along with a short list of nodes you were creating that seemed to be slowing things down please?

0 Likes
Message 7 of 14

syracoj
Autodesk
Autodesk

What makes you say this Maxime? Is it just because of the performance degradation you are experiencing?

0 Likes
Message 8 of 14

syracoj
Autodesk
Autodesk

hmmm....

perhaps I have found a case where a new node created is triggering a recompile. 

Will talk to dev today.

0 Likes
Message 9 of 14

mjcg91
Collaborator
Collaborator

In a large graph (like a simulation solver setup), when getting a new node from the tab menu, it takes ~1 second to see the node appear, whereas in a clean graph, the node appear instantly. 

 

I saw some case where it takes even longer, but I was not able to reproduce this.

Maxime Jeanmougin - Technical Artist
https://maximejeanmougin.com

Join the Bifrost Addicts community on Discord:
https://discord.gg/bifrost-addicts
0 Likes
Message 10 of 14

syracoj
Autodesk
Autodesk

@Anonymous 

@mjcg91 

 

We have found a couple cases where graph recompilation is occurring. 

Do you guys by any chance remember which nodes or compounds you were creating when you noticed the slowdown?

 

The two cases we identified have been logged. Just wanted to pick your brains on which nodes you guys experienced this with (if you can remember) so as not to miss something.

 

thanks.

0 Likes
Message 11 of 14

mjcg91
Collaborator
Collaborator

I think it might have been a basic math node like add or multiply,  but honestly I can't remember.

Maxime Jeanmougin - Technical Artist
https://maximejeanmougin.com

Join the Bifrost Addicts community on Discord:
https://discord.gg/bifrost-addicts
0 Likes
Message 12 of 14

wuhailu
Advocate
Advocate

My scene has a simple terrain deformer, but whenever I create an unconnected complex composite node, the Bifrost engine will be triggered.

bifrost地形.png

0 Likes
Message 13 of 14

syracoj
Autodesk
Autodesk

@wuhailu 

what do you mean by composite node?

 

I see you have a create_mesh_plane. I identified that graph gets recompiled if a create_mesh_* gets created (even if it's not connected) in the bifrost graph so you might be encountering the already understood case. I'll rebuild your graph none the less and see what happens.

 

thanks!

0 Likes
Message 14 of 14

syracoj
Autodesk
Autodesk

@wuhailu 

I was able to encounter several situations where the graph recompiles even on a scene that has a create_mesh_plane simply connected to the output node. I talked to dev and they have confirmed that this is the same underlying issue with our already logged issue. So we should be fixing this shortly. thanks.

0 Likes