Regression: Blender 3.1 UI editor resize /border dragging performance #97272

Open
opened 2022-04-12 10:15:11 +02:00 by Ludvik Koutny · 24 comments
Contributor

System Information
Operating system: Windows-10-10.0.19044-SP0 64 Bits
Graphics card: NVIDIA GeForce RTX 2080 Ti/PCIe/SSE2 NVIDIA Corporation 4.5.0 NVIDIA 512.15

Blender Version
Broken: version: 3.1.2, branch: master, commit date: 2022-03-31 17:40, hash: cc66d1020c
Worked: 3.0.1

Caused by {6738ecb64e8b6d0c1f5a79f1e63f468b4138de19}

Short description of error
Resizing UI editor panels in Blender 3.1 is significantly slower (framerate) and laggier than it was in 3.0. This is not related to the UV Editor performance regression as it happens even when there's no UV editor displayed in the given workspace.

Here's a video of the issue, recorded at 60FPS and slowed down to 50% so the issue is more apparent: https://www.youtube.com/watch?v=a0wzLgkf6mk

Exact steps for others to reproduce the error

  1. Open blender with a new empty file
  2. Drag the top of the Timeline Editor UI area around
    Result: The UI redraw framerate and input response (lag) are worse than in Blender 3.0
    Expected: The UI redraw framerate and input response (lag) are same or better than in Blender 3.0
**System Information** Operating system: Windows-10-10.0.19044-SP0 64 Bits Graphics card: NVIDIA GeForce RTX 2080 Ti/PCIe/SSE2 NVIDIA Corporation 4.5.0 NVIDIA 512.15 **Blender Version** Broken: version: 3.1.2, branch: master, commit date: 2022-03-31 17:40, hash: `cc66d1020c` Worked: 3.0.1 Caused by {6738ecb64e8b6d0c1f5a79f1e63f468b4138de19} **Short description of error** Resizing UI editor panels in Blender 3.1 is significantly slower (framerate) and laggier than it was in 3.0. This is not related to the UV Editor performance regression as it happens even when there's no UV editor displayed in the given workspace. Here's a video of the issue, recorded at 60FPS and slowed down to 50% so the issue is more apparent: https://www.youtube.com/watch?v=a0wzLgkf6mk **Exact steps for others to reproduce the error** 1. Open blender with a new empty file 2. Drag the top of the Timeline Editor UI area around Result: The UI redraw framerate and input response (lag) are worse than in Blender 3.0 Expected: The UI redraw framerate and input response (lag) are same or better than in Blender 3.0
Author
Contributor

Added subscriber: @Rawalanche

Added subscriber: @Rawalanche

#97680 was marked as duplicate of this issue

#97680 was marked as duplicate of this issue
Member

Added subscribers: @Jeroen-Bakker, @lichtwerk

Added subscribers: @Jeroen-Bakker, @lichtwerk
Member

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

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

This is apparently caused by {6738ecb64e8b6d0c1f5a79f1e63f468b4138de19}

Think this already mentioned in #95428 (Regression: 3.1 & 3.2 Image/UV Editor poor performance (Byte textures, window dragging, maximizing area)) Test 2 though... Maybe we should split these up in two reports, @Jeroen-Bakker?

This is apparently caused by {6738ecb64e8b6d0c1f5a79f1e63f468b4138de19} Think this already mentioned in #95428 (Regression: 3.1 & 3.2 Image/UV Editor poor performance (Byte textures, window dragging, maximizing area)) `Test 2` though... Maybe we should split these up in two reports, @Jeroen-Bakker?
Philipp Oeser changed title from Blender 3.1 UI editor resize performance regression to Blender 3.1 UI editor resize /border dragging performance regression 2022-04-12 12:48:06 +02:00
Philipp Oeser changed title from Blender 3.1 UI editor resize /border dragging performance regression to Regression: Blender 3.1 UI editor resize /border dragging performance 2022-04-12 14:50:01 +02:00

Added subscriber: @Xorrito

Added subscriber: @Xorrito

Added subscriber: @RafaelPasquay-2

Added subscriber: @RafaelPasquay-2
Member

Added subscriber: @oliveiralberto

Added subscriber: @oliveiralberto

Added subscriber: @Julian-Szigethy

Added subscriber: @Julian-Szigethy
Member

Although I see that there is a difference. The change that introduces the regression fixes a much higher prio bug. I suggest that we keep this around until we need to support these faulty OpenGL platforms.

Although I see that there is a difference. The change that introduces the regression fixes a much higher prio bug. I suggest that we keep this around until we need to support these faulty OpenGL platforms.
Member

In #97272#1350749, @Jeroen-Bakker wrote:
Although I see that there is a difference. The change that introduces the regression fixes a much higher prio bug. I suggest that we keep this around until we need to support these faulty OpenGL platforms.

Could 6738ecb64e be made platform specific then (so not everyone has to suffer from this)?

> In #97272#1350749, @Jeroen-Bakker wrote: > Although I see that there is a difference. The change that introduces the regression fixes a much higher prio bug. I suggest that we keep this around until we need to support these faulty OpenGL platforms. Could 6738ecb64e be made platform specific then (so not everyone has to suffer from this)?
Author
Contributor

This doesn't make sense. So we get very severely reduced performance across the entire Blender UI just because someone's obscure old laptop GPU had a driver issue? O_o

This doesn't make sense. So we get very severely reduced performance across the entire Blender UI just because someone's obscure old laptop GPU had a driver issue? O_o

Added subscriber: @Slowwkidd

Added subscriber: @Slowwkidd

Too bad this is not considered a high priority, Blender always had smoothness in its UI as one of its cornerstones, it's a pity we had such a downgrade and the devs don't feel the need to fix this as soon as possible. Between this and the UV/mage Editor regression, I feel the features of this last release are overshadowed by these UI important downgrades. I hope that at least for 3.2 this will be fixed.

Too bad this is not considered a high priority, Blender always had smoothness in its UI as one of its cornerstones, it's a pity we had such a downgrade and the devs don't feel the need to fix this as soon as possible. Between this and the UV/mage Editor regression, I feel the features of this last release are overshadowed by these UI important downgrades. I hope that at least for 3.2 this will be fixed.
Author
Contributor

This issue is even worse, as it causes very short but very uncomfortable lag when adding new nodes inside a node editor. Just in general, the node editor now suffers from frustrating short lags.

This issue is even worse, as it causes very short but very uncomfortable lag when adding new nodes inside a node editor. Just in general, the node editor now suffers from frustrating short lags.
Member

Added subscriber: @HooglyBoogly

Added subscriber: @HooglyBoogly
Jeroen Bakker self-assigned this 2022-05-10 08:07:45 +02:00
Member

I have been checking around and it seems to be that on my system the lag isn't that bad as on other work stations. I am looking into something that will remove this on workaround in known cases.
Thanks for your patience!

I have been checking around and it seems to be that on my system the lag isn't that bad as on other work stations. I am looking into something that will remove this on workaround in known cases. Thanks for your patience!

This issue was referenced by 439f86ac89

This issue was referenced by 439f86ac89bdd649aa9ccfe258c5f80474788449
Member

@Rawalanche that doesn't seem related to this issue. could you report it in a new issue?
@Slowwkidd I find that a not running system (crashes, shader compilations errors, malfunctioning functionality) is more important that a performance regression. I mean with the other you cannot work, with a performance regression it is annoying, but you can still work.
I think that anyone would agree with that. So when having limited time I prefer to work on the first category of issues.

Although we haven't been able to reproduce this issue on multiple machines in the studio I will commit a potential fix.
As we aren't able to reproduce it is very hard for a developer to fix this. On my machine (Linux AMD Ryzen 3800, NVIDIA 1080) that is fixed to 60fps I get 60fps when resizing a viewport (except the uv/image editor or when using eevee) for the uv/image editor I get 30 fps.

@Rawalanche that doesn't seem related to this issue. could you report it in a new issue? @Slowwkidd I find that a not running system (crashes, shader compilations errors, malfunctioning functionality) is more important that a performance regression. I mean with the other you cannot work, with a performance regression it is annoying, but you can still work. I think that anyone would agree with that. So when having limited time I prefer to work on the first category of issues. Although we haven't been able to reproduce this issue on multiple machines in the studio I will commit a potential fix. As we aren't able to reproduce it is very hard for a developer to fix this. On my machine (Linux AMD Ryzen 3800, NVIDIA 1080) that is fixed to 60fps I get 60fps when resizing a viewport (except the uv/image editor or when using eevee) for the uv/image editor I get 30 fps.
Author
Contributor

@Jeroen-Bakker I could, if you want me to, but this issue is reproducible in exactly the same build as the resize lag issue. When I test the blender builds prior to the change, the lag when adding new nodes is not there either.

@Jeroen-Bakker I could, if you want me to, but this issue is reproducible in exactly the same build as the resize lag issue. When I test the blender builds prior to the change, the lag when adding new nodes is not there either.
Member

Would be great if you could @Rawalanche

Would be great if you could @Rawalanche

Added subscriber: @JanKaderabek

Added subscriber: @JanKaderabek
Author
Contributor

In #97272#1355577, @Jeroen-Bakker wrote:
Would be great if you could @Rawalanche

Hi,

while trying to reproduce it, I found out that it was caused by the per-application nVidia driver power management mode being reset to default value, after doing a clean driver reinstall earlier. This setting is known to cause some lag in Blender, and it seems it has aggravated the performance issues.
image.png
This is my bad. While the power management mode does not solve the UI border resize lag, it did solve the short lag after adding the nodes. So nevermind :)

> In #97272#1355577, @Jeroen-Bakker wrote: > Would be great if you could @Rawalanche Hi, while trying to reproduce it, I found out that it was caused by the per-application nVidia driver power management mode being reset to default value, after doing a clean driver reinstall earlier. This setting is known to cause some lag in Blender, and it seems it has aggravated the performance issues. ![image.png](https://archive.blender.org/developer/F13067074/image.png) This is my bad. While the power management mode does not solve the UI border resize lag, it did solve the short lag after adding the nodes. So nevermind :)
Member

@Rawalanche thanks for letting us know!

@Rawalanche thanks for letting us know!
Jeroen Bakker removed their assignment 2022-05-18 16:33:14 +02:00
Philipp Oeser removed the
Interest
EEVEE & Viewport
label 2023-02-09 15:12:41 +01:00
Sign in to join this conversation.
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
10 Participants
Notifications
Due Date
The due date is invalid or out of range. Please use the format 'yyyy-mm-dd'.

No due date set.

Dependencies

No dependencies set.

Reference: blender/blender#97272
No description provided.