EEVEE Material Preview works significantly slower than before. #95600

New Issue

Matt Nomatter · 2022-02-08T07:46:45+01:00

Matt Nomatter commented

2022-02-08 07:46:45 +01:00

System Information
Operating system: MacOS Mojave 10.14.6 (18G9323)
Graphics card: Intel Iris Graphics 550 1536 MB
Memory: 16 GB 2133 MHz LPDDR3
Processor: 3,3 GHz Intel Core i7

Blender Version
Broken: (example: 3.0.1, 2.93.8 edbf15d3c0, master, 2018-11-28, as found on the splash screen)
Worked: 2.83.19

Short description of error
Switching to "Material Preview" view mode (or Rendered) and any manipulation of a material (like adding new node) takes significantly longer than in previous version.

Exact steps for others to reproduce the error

Open attached file
Click "Material Preview" view mode
Wait until material is fully visible in the viewport

I know my machine is not a great performance beast and my OS is pretty outdated (but I can't upgrade because of other apps that I use), but you can clearly tell that 3.0.1 works much slower. I tried also 2.93.8 version (LTS tab on blender.org) and the result is the same. Only 2.83.19 worked faster. I attached a video, it's realtime screen recording (the only editing within the video is blurring the mess on my desktop). Also you can find a blend file that was use to perform the test. performance-test.blend

blender_performance.mp4

**System Information** Operating system: MacOS Mojave 10.14.6 (18G9323) Graphics card: Intel Iris Graphics 550 1536 MB Memory: 16 GB 2133 MHz LPDDR3 Processor: 3,3 GHz Intel Core i7 **Blender Version** Broken: (example: 3.0.1, 2.93.8 edbf15d3c044, master, 2018-11-28, as found on the splash screen) Worked: 2.83.19 **Short description of error** Switching to "Material Preview" view mode (or Rendered) and any manipulation of a material (like adding new node) takes significantly longer than in previous version. **Exact steps for others to reproduce the error** 1. Open attached file 2. Click "Material Preview" view mode 3. Wait until material is fully visible in the viewport I know my machine is not a great performance beast and my OS is pretty outdated (but I can't upgrade because of other apps that I use), but you can clearly tell that 3.0.1 works much slower. I tried also 2.93.8 version (LTS tab on blender.org) and the result is the same. Only 2.83.19 worked faster. I attached a video, it's realtime screen recording (the only editing within the video is blurring the mess on my desktop). Also you can find a blend file that was use to perform the test. [performance-test.blend](https://archive.blender.org/developer/F12854620/performance-test.blend) [blender_performance.mp4](https://archive.blender.org/developer/F12854616/blender_performance.mp4)

Matt Nomatter commented

2022-02-08 07:46:45 +01:00

Added subscriber: @Matt-Nomatter

Matt Nomatter commented

2022-02-08 07:58:49 +01:00

few more things that came to my mind:

if you're surprised my desktop wallpaper changed - I just have automatically changing wallpaper every few minutes. the video is uncut.
this file was created in 3.0.1, but the issue is the same with files that I previously created in 2.83.x
render single frame time jumped from 4-5s (2.83.19) to 11-12s (3.0.1)

few more things that came to my mind: 1. if you're surprised my desktop wallpaper changed - I just have automatically changing wallpaper every few minutes. the video is uncut. 2. this file was created in 3.0.1, but the issue is the same with files that I previously created in 2.83.x 3. render single frame time jumped from 4-5s (2.83.19) to 11-12s (3.0.1)

Omar Emara commented

2022-02-08 09:11:19 +01:00

Added subscriber: @OmarEmaraDev

Omar Emara commented

2022-02-08 09:11:19 +01:00

Changed status from 'Needs Triage' to: 'Needs Developer To Reproduce'

Omar Emara commented

2022-02-08 09:11:19 +01:00

There is indeed a sizable difference between shader preparation/compilation time in 2.83 and later versions. It could be that more work is being done, but we should ask a developed if this is expected or not.

Jeroen Bakker commented

2022-02-08 10:00:50 +01:00

Added subscriber: @Jeroen-Bakker

Jeroen Bakker commented

2022-02-08 10:00:50 +01:00

I suspect D10390: EEVEE: Refactor closure_lit_lib.glsl. Sometimes tradeoff have to be made in terms between maintainability and platform performance. In blender we try to optimize for newer platforms. Older platforms can become slower as their drivers don't receive the optimizations we are targeting (responsibility of the OS driver developer). If the closure lit refactor is the root cause fixing this would slow down other platforms as that was the goal of the task.

The good news is that #93220 (EEVEE rewrite) will be improved compilation times.

I suspect [D10390: EEVEE: Refactor closure_lit_lib.glsl](https://archive.blender.org/developer/D10390). Sometimes tradeoff have to be made in terms between maintainability and platform performance. In blender we try to optimize for newer platforms. Older platforms can become slower as their drivers don't receive the optimizations we are targeting (responsibility of the OS driver developer). If the closure lit refactor is the root cause fixing this would slow down other platforms as that was the goal of the task. The good news is that #93220 (EEVEE rewrite) will be improved compilation times.

Matt Nomatter commented

2022-02-08 12:25:39 +01:00

In #95600#1303770, @Jeroen-Bakker wrote:
I suspect D10390: EEVEE: Refactor closure_lit_lib.glsl. Sometimes tradeoff have to be made in terms between maintainability and platform performance. In blender we try to optimize for newer platforms. Older platforms can become slower as their drivers don't receive the optimizations we are targeting (responsibility of the OS driver developer). If the closure lit refactor is the root cause fixing this would slow down other platforms as that was the goal of the task.

The good news is that #93220 (EEVEE rewrite) will be improved compilation times.

is there anything else for now that I can do? I totally understand the approach the dev team has, that's fair. I just stuck for now with mojave OS and I can't really help it. To be frank, the only thing that I miss in 2.83 is the Asset Browser, except that I could live with old version until v3.2 (as I checked that's when EEVEE would be rewritten) or there's a chance I'd upgrade my setup by then. Any advice for short term solution?

> In #95600#1303770, @Jeroen-Bakker wrote: > I suspect [D10390: EEVEE: Refactor closure_lit_lib.glsl](https://archive.blender.org/developer/D10390). Sometimes tradeoff have to be made in terms between maintainability and platform performance. In blender we try to optimize for newer platforms. Older platforms can become slower as their drivers don't receive the optimizations we are targeting (responsibility of the OS driver developer). If the closure lit refactor is the root cause fixing this would slow down other platforms as that was the goal of the task. > > The good news is that #93220 (EEVEE rewrite) will be improved compilation times. is there anything else for now that I can do? I totally understand the approach the dev team has, that's fair. I just stuck for now with mojave OS and I can't really help it. To be frank, the only thing that I miss in 2.83 is the Asset Browser, except that I could live with old version until v3.2 (as I checked that's when EEVEE would be rewritten) or there's a chance I'd upgrade my setup by then. Any advice for short term solution?

Omar Emara commented

2022-02-08 17:44:01 +01:00

@Matt-Nomatter I suspect the requirements for EEVEE are only going to get higher, so I wouldn't expected older hardware to fair better in the future even with the rewrite, so that's something to keep in mind.

Philipp Oeser removed the

Download

What's New

Blender Studio

Manual

Developers Blog

Documentation

Benchmark

Blender Conference

Development Fund

One-time Donations

EEVEE Material Preview works significantly slower than before. #95600