Complex scenes cause node editor interactions to be very laggy #67429

New Issue

Ludvik Koutny · 2019-07-22T09:48:28+02:00

Ludvik Koutny commented

2019-07-22 09:48:28 +02:00

System Information
Operating system: Windows-10-10.0.17763 64 Bits
Graphics card: GeForce GTX 1080 Ti/PCIe/SSE2 NVIDIA Corporation 4.5.0 NVIDIA 430.64

Blender Version
Broken: version: 2.80 (sub 74), branch: master, commit date: 2019-07-18 14:52, hash: 38d4483c6a
Worked: (optional)

Short description of error
I have some more complex scenes where the node editor interactions are quite laggy even if the 3D viewport is not part of the layout at all. Simple things like dragging selection box or moving around nodes in viewport cause stutter and UI lag. Pretty much any mouse cursor interaction with node editor does.

Exact steps for others to reproduce the error

In a new .blend file, subdivide the default cube several times, so it has around 25k polygons
Duplicate (not instantiate) this cube about 500 times
Select about half (250) of the cubes, and parent them to one of the cubes
Select other half of the cubes, and again, parent them to one another cube
You should have two cubes each with around 249 children.
Select one random cube, and assign a new material to it
Open node editor and interact with the material.
Notice the node editor interaction is very laggy
Create a new cube, that is not parented to anything (not part of the complex hierarchy)
Assign a new material to it
Notice the node editor interaction is still extremely laggy
Remove 3D view from the active workspace
Notice the node editor interaction is still extremely laggy

Result: The sheer complexity of the scene causes node editor interaction to be very laggy, even when using node editor to interact with nodes which are not a direct part of the scene complexity (A new unique material on a new unique cube with a new unique mesh data block). Also, removing 3D viewport from the workspace layout does not help.

Expected: Node editor interaction remains smooth regardless of scene complexity

It appears that every single UI interaction such as mouse click in the node editor is evaluating a lot more data than it needs to.

**System Information** Operating system: Windows-10-10.0.17763 64 Bits Graphics card: GeForce GTX 1080 Ti/PCIe/SSE2 NVIDIA Corporation 4.5.0 NVIDIA 430.64 **Blender Version** Broken: version: 2.80 (sub 74), branch: master, commit date: 2019-07-18 14:52, hash: `38d4483c6a` Worked: (optional) **Short description of error** I have some more complex scenes where the node editor interactions are quite laggy even if the 3D viewport is not part of the layout at all. Simple things like dragging selection box or moving around nodes in viewport cause stutter and UI lag. Pretty much any mouse cursor interaction with node editor does. **Exact steps for others to reproduce the error** 1. In a new .blend file, subdivide the default cube several times, so it has around 25k polygons 2. Duplicate (not instantiate) this cube about 500 times 3. Select about half (250) of the cubes, and parent them to one of the cubes 4. Select other half of the cubes, and again, parent them to one another cube 5. You should have two cubes each with around 249 children. 7. Select one random cube, and assign a new material to it 8. Open node editor and interact with the material. 9. Notice the node editor interaction is very laggy 10. Create a new cube, that is not parented to anything (not part of the complex hierarchy) 11. Assign a new material to it 12. Notice the node editor interaction is still extremely laggy 13. Remove 3D view from the active workspace 14. Notice the node editor interaction is still extremely laggy Result: The sheer complexity of the scene causes node editor interaction to be very laggy, even when using node editor to interact with nodes which are not a direct part of the scene complexity (A new unique material on a new unique cube with a new unique mesh data block). Also, removing 3D viewport from the workspace layout does not help. Expected: Node editor interaction remains smooth regardless of scene complexity It appears that every single UI interaction such as mouse click in the node editor is evaluating a lot more data than it needs to.

Ludvik Koutny commented

2019-07-22 09:48:28 +02:00

Added subscriber: @Rawalanche

Ludvik Koutny changed title from ~~Complex scenes cause node editor interactions to be laggy~~ to Complex scenes cause node editor interactions to be very laggy

2019-07-22 09:57:37 +02:00

Marcus Papathoma commented

2019-07-22 11:09:56 +02:00

Added subscriber: @machieb

Marcus Papathoma commented

2019-07-22 11:09:56 +02:00

I´m working with around 20million polygons and around 10000objects every day. The node editor is then most of the time very laggy.
So I can confirm that that the interaction in the node editor is very laggy when working in complex scenes.

Operating system: Windows-10-10.0.17134 64 Bits
Graphics card: GeForce GTX TITAN X/PCIe/SSE2 NVIDIA Corporation 4.5.0 NVIDIA 430.86
Graphics card: GeForce GTX 1080TI/PCIe/SSE2 NVIDIA Corporation 4.5.0 NVIDIA 430.86

I´m working with around 20million polygons and around 10000objects every day. The node editor is then most of the time very laggy. So I can confirm that that the interaction in the node editor is very laggy when working in complex scenes. Operating system: Windows-10-10.0.17134 64 Bits Graphics card: GeForce GTX TITAN X/PCIe/SSE2 NVIDIA Corporation 4.5.0 NVIDIA 430.86 Graphics card: GeForce GTX 1080TI/PCIe/SSE2 NVIDIA Corporation 4.5.0 NVIDIA 430.86

Brecht Van Lommel was assigned by Sebastian Parborg

2019-07-30 16:52:13 +02:00

Brecht Van Lommel commented

2019-09-16 18:34:22 +02:00

Changed status from 'Open' to: 'Archived'

Brecht Van Lommel closed this issue

2019-09-16 18:34:22 +02:00

Brecht Van Lommel commented

2019-09-16 18:34:22 +02:00

Profiling shows that this is related to undo system writing, particularly since it happens when the 3D viewport is hidden.

For that we have #60695 (Optimized per-datablock global undo), the third step there is what would address this case.

Profiling shows that this is related to undo system writing, particularly since it happens when the 3D viewport is hidden. For that we have #60695 (Optimized per-datablock global undo), the third step there is what would address this case.

Sign in to join this conversation.

No Label

Download

What's New

Blender Studio

Manual

Developers Blog

Documentation

Benchmark

Blender Conference

Development Fund

One-time Donations

Complex scenes cause node editor interactions to be very laggy #67429