Performance regression with subdivision modifier and enabled scene statistics #94671

New Issue

thin soldier · 2022-01-05T22:57:10+01:00

thin soldier commented

2022-01-05 22:57:10 +01:00

System Information
Operating system: Windows-10-10.0.19043-SP0 64 Bits
Graphics card: NVIDIA GeForce GTX 1650/PCIe/SSE2 NVIDIA Corporation 4.5.0 NVIDIA 472.84

Blender Version
Broken: version: 3.1.0, caused by {eed45d2a239a2a18a2420ba15dfb55e0f8dc5630} or maybe {d25fa3250aae7e22f68579c053c591a8b2682e3c}
NOTE: For eed45d2a23 or later commits, I had to apply d25fa3250a to avoid deadlock

Short description of error
Enabled scene statistics along with objects with Subdivision Surface modifier makes viewport lagging, including at least node editor.
With CPU subdivision viewport lagging occur no matter if modifier enabled in viewport or not. With GPU subdivision issue occur only when modifier is disabled in viewport (perhaps another bug?).

Exact steps for others to reproduce the error

Open attached file
Enable scene statistics (RMB over the footer or via overlay)
Move around the Cube.
Viewport has very visible lag.

NOTE: The problem occurs even if the modifier is disabled or if GPU Subdvision is enabled in the preferences.

viewport_statistics_lag.blend

**System Information** Operating system: Windows-10-10.0.19043-SP0 64 Bits Graphics card: NVIDIA GeForce GTX 1650/PCIe/SSE2 NVIDIA Corporation 4.5.0 NVIDIA 472.84 **Blender Version** Broken: version: 3.1.0, caused by {eed45d2a239a2a18a2420ba15dfb55e0f8dc5630} or maybe {d25fa3250aae7e22f68579c053c591a8b2682e3c} NOTE: For eed45d2a23 or later commits, I had to apply d25fa3250a to avoid deadlock **Short description of error** Enabled scene statistics along with objects with `Subdivision Surface` modifier makes viewport lagging, including at least node editor. With CPU subdivision viewport lagging occur no matter if modifier enabled in viewport or not. With GPU subdivision issue occur only when modifier is disabled in viewport (perhaps another bug?). **Exact steps for others to reproduce the error** - Open attached file - Enable scene statistics (RMB over the footer or via overlay) - Move around the Cube. Viewport has very visible lag. NOTE: The problem occurs even if the modifier is disabled or if `GPU Subdvision` is enabled in the preferences. [viewport_statistics_lag.blend](https://archive.blender.org/developer/F12799111/viewport_statistics_lag.blend)

thin soldier commented

2022-01-05 22:57:10 +01:00

Added subscriber: @thinsoldier

blender-admin commented

2022-01-05 22:57:10 +01:00

#94608 was marked as duplicate of this issue

Richard Antalik commented

2022-01-06 03:52:51 +01:00

Added subscriber: @iss

Richard Antalik commented

2022-01-06 03:52:51 +01:00

Changed status from 'Needs Triage' to: 'Needs User Info'

Richard Antalik commented

2022-01-06 03:52:51 +01:00

I can't reproduce this issue here

System Information
Operating system: Windows-10-10.0.19041-SP0 64 Bits
Graphics card: NVIDIA GeForce RTX 3060/PCIe/SSE2 NVIDIA Corporation 4.5.0 NVIDIA 472.12
version: 3.1.0 Alpha, branch: master, commit date: 2022-01-03 07:10, hash: ea8d749587

#94671.blend

@thinsoldier Can you check if I followed your steps correctly? Also I can see some operation will result in small lag, but then everything is quite smooth.

I can't reproduce this issue here **System Information** Operating system: Windows-10-10.0.19041-SP0 64 Bits Graphics card: NVIDIA GeForce RTX 3060/PCIe/SSE2 NVIDIA Corporation 4.5.0 NVIDIA 472.12 version: 3.1.0 Alpha, branch: master, commit date: 2022-01-03 07:10, hash: `ea8d749587` [#94671.blend](https://archive.blender.org/developer/F12790934/T94671.blend) @thinsoldier Can you check if I followed your steps correctly? Also I can see some operation will result in small lag, but then everything is quite smooth.

thin soldier commented

2022-01-07 04:56:08 +01:00

Hi Richard. Your file is correct.

Opening your file took almost a minute. Selecting the cube took 4 seconds. Deselecting the cube took 3 seconds. Same with the monkey. Moving the cube is a chore.
Double clicking the cube in the outliner to rename it does not work. If I double click on the cube in the outliner and then move my mouse over the camera, after about 6 seconds the camera gets selected.

If I go to preferences to enable gpu subdivision option it takes about 8 seconds for the checkbox to become active. It then takes about 8 seconds to go back to the main blender window. After that, all problems are gone.

Opening the file in Blender 3.0 only takes 10 seconds and has no problems interacting with anything.

I am currently downloading the latest build e6ca0b33e9 to test your file again.

Update: I was certain I had used factory settings in my testing but I guess I was wrong. After using Load Factory Settings there doesn't seem to be any problems. I'll try to figure out which addon brings the problem back.

Update 2: I went back to my previous settings and then I disabled every addon one by one and check performance and nothing improved. Other observations: pan/zoom/orbit has no problems, entering edit mode on the cube is fast, leaving edit mode takes 3 seconds. Move/rotate/scale of cube components in edit mode is fast. While in edit mode on the cube, interacting with properties sliders or renaming items in the outliner is fast like normal.

Update 3: Load Factory Settings enables the GPU Subdivision option which explains why the problem went away in that case.

Hi Richard. Your file is correct. Opening your file took almost a minute. Selecting the cube took 4 seconds. Deselecting the cube took 3 seconds. Same with the monkey. Moving the cube is a chore. Double clicking the cube in the outliner to rename it does not work. If I double click on the cube in the outliner and then move my mouse over the camera, after about 6 seconds the camera gets selected. If I go to preferences to enable gpu subdivision option it takes about 8 seconds for the checkbox to become active. It then takes about 8 seconds to go back to the main blender window. After that, all problems are gone. Opening the file in Blender 3.0 only takes 10 seconds and has no problems interacting with anything. I am currently downloading the latest build e6ca0b33e920 to test your file again. Update: I was certain I had used factory settings in my testing but I guess I was wrong. After using Load Factory Settings there doesn't seem to be any problems. I'll try to figure out which addon brings the problem back. Update 2: I went back to my previous settings and then I disabled every addon one by one and check performance and nothing improved. Other observations: pan/zoom/orbit has no problems, entering edit mode on the cube is fast, leaving edit mode takes 3 seconds. Move/rotate/scale of cube components in edit mode is fast. While in edit mode on the cube, interacting with properties sliders or renaming items in the outliner is fast like normal. Update 3: Load Factory Settings enables the GPU Subdivision option which explains why the problem went away in that case.

Lyaka commented

2022-01-07 11:00:42 +01:00

Added subscriber: @qbicksan

Lyaka commented

2022-01-07 11:00:42 +01:00

Even with GPU Subdivision turned on it is still very laggy, check this video:

https://drive.google.com/file/d/1IASDCiYFiXiRTCHamgjjyeynx4n6qI-r/view?usp=drivesdk

with lots of subdivided items it is almost impossible to position objects, but with subdiv being applied - everything is snappy.
however, if I was about to position all polygons of given item instead of moving object - no lags at all.

Even with GPU Subdivision turned on it is still **very** laggy, check this video: https://drive.google.com/file/d/1IASDCiYFiXiRTCHamgjjyeynx4n6qI-r/view?usp=drivesdk with lots of subdivided items it is almost impossible to position objects, but with subdiv being applied - everything is snappy. however, if I was about to position all polygons of given item instead of moving object - no lags at all.

Richard Antalik commented

2022-01-08 04:30:28 +01:00

Changed status from 'Needs User Info' to: 'Needs Triage'

Richard Antalik commented

2022-01-08 04:30:28 +01:00

Checked this with fairly low performance notebook too and can't really see any significant difference between 3.0 and 3.1 versions.

Vyacheslav Kobozev commented

2022-01-08 08:07:17 +01:00

Added subscriber: @Vyach

Vyacheslav Kobozev commented

2022-01-08 08:07:17 +01:00

2022-01-08_10-04-26.mp4

[2022-01-08_10-04-26.mp4](https://archive.blender.org/developer/F12794094/2022-01-08_10-04-26.mp4)

Garek commented

2022-01-08 11:06:49 +01:00

Added subscribers: @kevindietrich, @Garek

Garek commented

2022-01-08 11:06:49 +01:00

Changed status from 'Needs Triage' to: 'Confirmed'

Garek commented

2022-01-08 11:06:49 +01:00

Can confirm. Will raise priority as this is confirmed regression.

Problem lies within scene statistics (both overlay and at the footer). That wasn't obvious since with Load Factory Settings all was working but without it did not. I remembered that only thing I changed before in startup file is scene statistics.
I noticed lag with moving nodes but didn't test it as much as just moving Suzanne, assume it's same.
I tried to reproduce with other modifiers such as Remesh and Multiresolution but they seems to work fine.

Blender 3.0 test
1. Blender 3.0 2022-01-08 14-25-22.mp4
Blender 3.1 CPU Subdivision
2. Blender 3.1 CPU 2022-01-08 14-28-06.mp4
Blender 3.1 GPU Subdivision. Notice that although while modifier is visible in viewport and working fine with statistics it still needs a lot of time to load upon checking scene statistics. And upon disabling modifier in viewport there is lag.
3. Blender 3.1 GPU 2022-01-08 14-32-31.mp4

Can confirm. Will raise priority as this is confirmed regression. Problem lies within scene statistics (both overlay and at the footer). That wasn't obvious since with `Load Factory Settings` all was working but without it did not. I remembered that only thing I changed before in startup file is scene statistics. I noticed lag with moving nodes but didn't test it as much as just moving Suzanne, assume it's same. I tried to reproduce with other modifiers such as Remesh and Multiresolution but they seems to work fine. 1. Blender 3.0 test [1. Blender 3.0 2022-01-08 14-25-22.mp4](https://archive.blender.org/developer/F12795291/1._Blender_3.0_2022-01-08_14-25-22.mp4) 2. Blender 3.1 CPU Subdivision [2. Blender 3.1 CPU 2022-01-08 14-28-06.mp4](https://archive.blender.org/developer/F12795305/2._Blender_3.1_CPU_2022-01-08_14-28-06.mp4) 3. Blender 3.1 GPU Subdivision. Notice that although while modifier is visible in viewport and working fine with statistics it still needs a lot of time to load upon checking scene statistics. And upon disabling modifier in viewport there is lag. [3. Blender 3.1 GPU 2022-01-08 14-32-31.mp4](https://archive.blender.org/developer/F12795323/3._Blender_3.1_GPU_2022-01-08_14-32-31.mp4)

Garek changed title from ~~performance regression when subdivision modifier is in use~~ to Performance regression with subdivision modifier and enabled scene statistics

2022-01-08 11:25:12 +01:00

Germano Cavalcante commented

2022-01-10 14:33:30 +01:00

Added subscribers: @MarcinTwarowski, @mano-wii