Performance degradation in the shader & geometry node editor for larger scenes between 3.1 & 3.2 #99299

New Issue

Mr Chocolate Bar · 2022-06-30T14:53:46+02:00

Mr Chocolate Bar commented

2022-06-30 14:53:46 +02:00

│Blender & System Information:                                                 │
│ * Blender Version:                                                           │
│   - 3, 2, 0                                                                  │
│ * Blender Last Commit Date:                                                  │
│   - 2022-06-08                                                               │
│ * Blender Build Hash:                                                        │
│   - e05e1e369187                                                             │
│ * Blender Branch:                                                            │
│   - master                                                                   │
│ * Blender Executable Location:                                               │
│   - F:\Olliver\Olliver\programs\Blender\blender-3.2.0-windows-x64\blender.exe│
│ * Python Version:                                                            │
│   - 3.10.2 (main, Jan 27 2022, 08:34:43) [MSC v.1928 64 bit (AMD64)]         │
│ * Platform this Blender instance was built for:                              │
│   - Windows                                                                  │
│ * Windows Platform Information:                                              │
│   - Caption=Microsoft Windows 11 Pro                                         │
│   - OSArchitecture=64-bit                                                    │
│   - Version=10.0.22000                                                       │
│ * Hardware Information:                                                      │
│   - GPU: NVIDIA GeForce GTX 1060 6GB/PCIe/SSE2                               │
│   - GPU Driver Version: NVIDIA Corporation 4.5.0 NVIDIA 511.79               │
│   - CPU MaxClockSpeed=3187                                                   │
│   - CPU Name=12th Gen Intel(R) Core(TM) i9-12900K                            │
│   - CPU NumberOfCores=16                                                     │
│   - Total System RAM: 34.088476672 GB                                        │
│                                                                              │
│This info text was generated by the Fast PBR Viewport Render addon!           │
└──────────────────────────────────────────────────────────────────────────────┘```

Demo file (sorry about the filesize, but the issue is not apparent in lighter scenes, all the content in this file is made by me in my freetime so I have full rights of uploading all of it): [levelMockup.zip](https://archive.blender.org/developer/F13242488/levelMockup.zip)

See: [WCSLS1ye25.mp4](https://archive.blender.org/developer/F13242477/WCSLS1ye25.mp4) ```┌──────────────────────────────────────────────────────────────────────────────┐ │Blender & System Information: │ │ * Blender Version: │ │ - 3, 2, 0 │ │ * Blender Last Commit Date: │ │ - 2022-06-08 │ │ * Blender Build Hash: │ │ - e05e1e369187 │ │ * Blender Branch: │ │ - master │ │ * Blender Executable Location: │ │ - F:\Olliver\Olliver\programs\Blender\blender-3.2.0-windows-x64\blender.exe│ │ * Python Version: │ │ - 3.10.2 (main, Jan 27 2022, 08:34:43) [MSC v.1928 64 bit (AMD64)] │ │ * Platform this Blender instance was built for: │ │ - Windows │ │ * Windows Platform Information: │ │ - Caption=Microsoft Windows 11 Pro │ │ - OSArchitecture=64-bit │ │ - Version=10.0.22000 │ │ * Hardware Information: │ │ - GPU: NVIDIA GeForce GTX 1060 6GB/PCIe/SSE2 │ │ - GPU Driver Version: NVIDIA Corporation 4.5.0 NVIDIA 511.79 │ │ - CPU MaxClockSpeed=3187 │ │ - CPU Name=12th Gen Intel(R) Core(TM) i9-12900K │ │ - CPU NumberOfCores=16 │ │ - Total System RAM: 34.088476672 GB │ │ │ │This info text was generated by the Fast PBR Viewport Render addon! │ └──────────────────────────────────────────────────────────────────────────────┘``` Demo file (sorry about the filesize, but the issue is not apparent in lighter scenes, all the content in this file is made by me in my freetime so I have full rights of uploading all of it): [levelMockup.zip](https://archive.blender.org/developer/F13242488/levelMockup.zip)

Mr Chocolate Bar commented

2022-06-30 14:53:46 +02:00

Added subscriber: @Olliver

Mr Chocolate Bar commented

2022-06-30 15:04:40 +02:00

I should add that the performance is not affected by any visible amount on my system even if I have the viewport up in material preview mode. If I were to do some incredibly naive guessing perhaps the "dont recompute the shaders if no viewport is visible" & "dont recompute the shader if the node modifications do not affect the end result" optimizations has been broken?

I should add that the performance is not affected by any visible amount on my system even if I have the viewport up in material preview mode. If I were to do some incredibly naive guessing *perhaps* the "dont recompute the shaders if no viewport is visible" & "dont recompute the shader if the node modifications do not affect the end result" optimizations has been broken?

Omar Emara commented

2022-07-04 15:30:44 +02:00

Added subscriber: @OmarEmaraDev

Omar Emara commented

2022-07-04 15:30:44 +02:00

This is probably the same as #98574, but the author reports the same in 3.1, so we shouldn't merge until this is investigated further.

Richard Antalik commented

2022-07-04 21:13:02 +02:00

Added subscriber: @iss

Richard Antalik commented

2022-07-04 21:13:02 +02:00

Checking with 3.3, can't reproduce any regression 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 511.65

Checking with 3.3, can't reproduce any regression 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 511.65

Germano Cavalcante commented

2022-07-05 18:09:42 +02:00

Added subscriber: @mano-wii

Germano Cavalcante commented

2022-07-05 18:09:42 +02:00

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

Germano Cavalcante commented

2022-07-05 18:09:42 +02:00

I compared 3.0 and 3.2 but didn't notice a difference. Although both had a delay in loading due to high memory consumption.
Task manager doesn't show any significant difference in memory usage in 3.2.

@Olliver, try the latest daily build: https://builder.blender.org/download/

Go to File → Defaults → Load Factory Settings and then load your file to see if you still can reproduce this issue.

I compared 3.0 and 3.2 but didn't notice a difference. Although both had a delay in loading due to high memory consumption. Task manager doesn't show any significant difference in memory usage in 3.2. @Olliver, try the latest daily build: https://builder.blender.org/download/ Go to File → Defaults → Load Factory Settings and then load your file to see if you still can reproduce this issue.

Mr Chocolate Bar commented

2022-07-05 20:17:49 +02:00

Unless anyone can link this to any particular commits, perhaps we could close this. The performance may be quite on pair on all versions now that I test again. 3.2 does seem a bit slower than other versions, but it is not quite that significant of a difference.

On the other hand, it would be nice if the node graphs were more responsive (especially when selecting & deselecting nodes as well as when performing a box selection). Its the slowest part of Blenders UI for large scenes.

Here is a second test I did today with the latest 3.3 from buildbot and comparing that with the same builds tested previously:

kk6Xajs8aN.mp4

Unless anyone can link this to any particular commits, perhaps we could close this. The performance may be quite on pair on all versions now that I test again. 3.2 does seem a bit slower than other versions, but it is not quite that significant of a difference. On the other hand, it would be nice if the node graphs were more responsive (especially when selecting & deselecting nodes as well as when performing a box selection). Its the slowest part of Blenders UI for large scenes. Here is a second test I did today with the latest 3.3 from buildbot and comparing that with the same builds tested previously: [kk6Xajs8aN.mp4](https://archive.blender.org/developer/F13261325/kk6Xajs8aN.mp4)

Omar Emara commented

2022-07-06 08:19:36 +02:00

There is a very similar report, so I will merge it that one instead of closing this.

Omar Emara commented

2022-07-06 08:19:46 +02:00

Closed as duplicate of #98574

Omar Emara closed this issue

2022-07-06 08:19:46 +02:00

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

Performance degradation in the shader & geometry node editor for larger scenes between 3.1 & 3.2 #99299