3.2 eevee bad performance #98865
Labels
No Label
Interest
Alembic
Interest
Animation & Rigging
Interest
Asset Browser
Interest
Asset Browser Project Overview
Interest
Audio
Interest
Automated Testing
Interest
Blender Asset Bundle
Interest
BlendFile
Interest
Collada
Interest
Compatibility
Interest
Compositing
Interest
Core
Interest
Cycles
Interest
Dependency Graph
Interest
Development Management
Interest
EEVEE
Interest
EEVEE & Viewport
Interest
Freestyle
Interest
Geometry Nodes
Interest
Grease Pencil
Interest
ID Management
Interest
Images & Movies
Interest
Import Export
Interest
Line Art
Interest
Masking
Interest
Metal
Interest
Modeling
Interest
Modifiers
Interest
Motion Tracking
Interest
Nodes & Physics
Interest
OpenGL
Interest
Overlay
Interest
Overrides
Interest
Performance
Interest
Physics
Interest
Pipeline, Assets & IO
Interest
Platforms, Builds & Tests
Interest
Python API
Interest
Render & Cycles
Interest
Render Pipeline
Interest
Sculpt, Paint & Texture
Interest
Text Editor
Interest
Translations
Interest
Triaging
Interest
Undo
Interest
USD
Interest
User Interface
Interest
UV Editing
Interest
VFX & Video
Interest
Video Sequencer
Interest
Virtual Reality
Interest
Vulkan
Interest
Wayland
Interest
Workbench
Interest: X11
Legacy
Blender 2.8 Project
Legacy
Milestone 1: Basic, Local Asset Browser
Legacy
OpenGL Error
Meta
Good First Issue
Meta
Papercut
Meta
Retrospective
Meta
Security
Module
Animation & Rigging
Module
Core
Module
Development Management
Module
EEVEE & Viewport
Module
Grease Pencil
Module
Modeling
Module
Nodes & Physics
Module
Pipeline, Assets & IO
Module
Platforms, Builds & Tests
Module
Python API
Module
Render & Cycles
Module
Sculpt, Paint & Texture
Module
Triaging
Module
User Interface
Module
VFX & Video
Platform
FreeBSD
Platform
Linux
Platform
macOS
Platform
Windows
Priority
High
Priority
Low
Priority
Normal
Priority
Unbreak Now!
Status
Archived
Status
Confirmed
Status
Duplicate
Status
Needs Info from Developers
Status
Needs Information from User
Status
Needs Triage
Status
Resolved
Type
Bug
Type
Design
Type
Known Issue
Type
Patch
Type
Report
Type
To Do
No Milestone
No project
No Assignees
15 Participants
Notifications
Due Date
No due date set.
Dependencies
No dependencies set.
Reference: blender/blender#98865
Loading…
Reference in New Issue
No description provided.
Delete Branch "%!s(<nil>)"
Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?
System Information
Operating system: Windows-10-10.0.19044-SP0 64 Bits
Graphics card: Radeon RX Vega ATI Technologies Inc. 4.5.14800 Core Profile Context 22.4.2 30.0.15021.7000
Blender Version
Broken: version: 3.2.0, branch: master, commit date: 2022-06-08 10:22, hash:
e05e1e3691
Worked: 3.1.2
Short description of error
Eevee is slower when compiling shaders and on viewport.
Compiling time has doubled and viewport feels laggy when zooming on small details.
Exact steps for others to reproduce the error
slow.blend
My compiling times went from ~10 seconds (3.1.2) to ~20 seconds (3.2) when limiting blender to one thread.
When disconnecting the bump node both compile in ~3 seconds.
I think it might be a combination of many nodes and bump node.
Added subscriber: @brunocb
#99163 was marked as duplicate of this issue
Added subscriber: @persun
System Information
Operating system: Windows-10-10.0.19043-SP0 64 Bits
Graphics card: Radeon RX 570 Series ATI Technologies Inc. 4.5.14800 Core Profile Context 22.5.1 30.0.15021.11005
I was feeling about this too. Yes, my GPU is old, low-end card and I was annoyed by shader compiles all the time but it's actually got worse .
I tried the file @brunocb attached and timed shader compile time (used smartphone's stopwatch, timed how much it takes from hitting the Material Preview button to actually showing the material.)
04a75c90d58a
, June 14th): 12-13sI also made a test file with little more complex, more "stressful" setup, using chains of bump nodes, procedural texture nodes, and a mix shader node.
bar.blend
Again, timed with the same method:
04a75c90d58a
, June 14th): 58-60sAdded subscriber: @kholo
System Information
Operating system: Linux-5.18.3-arch1-1-x86_64-with-glibc2.35 64 Bits
Graphics card: NVIDIA GeForce GTX 1660 Ti/PCIe/SSE2 NVIDIA Corporation 4.5.0 NVIDIA 515.48.07
Blender Version
Broken: version: 3.2.0, branch: makepkg (modified), commit date: 2022-06-08 10:22, hash:
e05e1e3691
Worked: version: 3.1.2, branch: master, commit date: 2022-03-31 17:40, hash:
cc66d1020c3b
Short description of error
I have a similar feeling here, although the compiling time was quite long for both, version 3.1.2 does not have to recompile them when re-opening the scene (cached). Version 3.2 recompile the whole set of shaders.
I tested one scene of mine with a heavy node graph, times were measured with a stopwatch once hitting the Material Preview button.
As for the viewport performances, version 3.1.2 offers realtime navigation, version 3.2 is really laggy.
Related reports #98901. #98989
Added subscribers: @fclem, @PratikPB2123
Changed status from 'Needs Triage' to: 'Needs Developer To Reproduce'
Thanks for the report
I've also noticed some differences in shader compiling between 3.2 and 3.1
I'm guessing the same commit as Germano said in #98901 :
80859a6cb2
@fclem , can you check?
Can confirm this as well
Added subscriber: @thilo.mack
Added subscriber: @Rodrigo_S.T
Added subscriber: @QBer
Added subscriber: @MACHIN3
Added subscriber: @geocentric_wage
Added subscriber: @AndreasResch
I hope something can be done about this. For comparison I opened the classroom scene and switched from Solid Mode to Material Preview Mode in Blender 2.79b and Blender 3.2.
Blender 2.79b - 7s
Blender 3.2 - 90s
Specs: Windows 10, Ryzen 3700X, 64GB RAM, RTX 3060
In general switching to Material Preview Mode takes between 30s in 120s. When you open dozens of scene each day, you can do the math how much time that costs. This is s serious problem and it hasn't been addressed in over a year now.
Added subscriber: @boydmouritsen
This one commit
80859a6cb2
seems to have caused some major performance regressions in various areas across Blender. How many does it have to have before it gets reverted? Something needs to be done, instead of ignoring it like we are doing now.
I'm really worried about this one because it will let me stack in V3.1 for very long time as my machine is quite new and no way to change it. Hope will get reverted back to as it was in next 3.3 release as is supposed to be LTS.
Added subscriber: @sozap
Added subscriber: @VerdeStudios
Closed as duplicate of #98989