Significant performance drop when changing the active render slot in 3.5 #107200

Closed
opened 2023-04-21 00:09:39 +02:00 by chaos · 3 comments
Member

System Information
Operating system: Linux-5.4.0-105-generic-x86_64-with-glibc2.31 64 Bits
Graphics card: NVIDIA GeForce RTX 3080 Ti/PCIe/SSE2 NVIDIA Corporation 4.5.0 NVIDIA 525.85.05

Blender Version
Broken: version: 3.5.0, branch: blender-v3.5-release, commit date: 2023-03-29 02:56, hash: 1be25cfff18b
Worked: version: 3.4.0, stable release

Description
There has been an important slowdown in the time it takes for Blender to set the active render slot in the last stable release of Blender 3.5, the performance was much better in Blender 3.4.
The size of the region area being shown in the UI seems to have something to do with this performance penalty.

I'm including a simple blend file with a test script to compare the times, so check the attachment.
The script adds a test modal operator that runs a fast timer and sets the active render slot in every modal loop.
The time is measured between every loop to get an idea of the FPS speed, and then this is shown in the area's header.

Exact steps for others to reproduce the error
You should repeat this test in Blender 3.5 and 3.4:

  • Open the blendfile
  • Run the script in the Text Editor
  • Put the cursor in the Image Editor with the Render Result image selected
  • Press F3 to search and run the operator "test.test". The FPS is now shown in the area's header
  • You can now change the size of the current Image Editor area while running the modal operator, for example, by dragging the area's border to change the size horizontally.
    This introduces the performance penalty, and you can see the reduction in FPS as the Image area gets bigger. When reducing the Image area, the speed increases again.
    This doesn't seem to happen in Blender 3.4, or at least it's imperceptible to me. In 3.4, the Image area can even be at fullscreen and I still can't see a reduction in speed, while in 3.5 the CPU works a lot harder and I can only get the same performance when reducing the size of the area up to a quarter compared to the original from 3.4.
  • Exit the modal loop with Esc key

What's the significance for the time it takes to set a render slot you may ask, and the thing is that I have a script that can change the slots rapidly, temporarily generating an animation with them, without having to export or save the frames. In the current state, it has just became too slow for that.

**System Information** Operating system: Linux-5.4.0-105-generic-x86_64-with-glibc2.31 64 Bits Graphics card: NVIDIA GeForce RTX 3080 Ti/PCIe/SSE2 NVIDIA Corporation 4.5.0 NVIDIA 525.85.05 **Blender Version** Broken: version: 3.5.0, branch: blender-v3.5-release, commit date: 2023-03-29 02:56, hash: `1be25cfff18b` Worked: version: 3.4.0, stable release **Description** There has been an important slowdown in the time it takes for Blender to set the active render slot in the last stable release of Blender 3.5, the performance was much better in Blender 3.4. The size of the region area being shown in the UI seems to have something to do with this performance penalty. I'm including a simple blend file with a test script to compare the times, so check the attachment. The script adds a test modal operator that runs a fast timer and sets the active render slot in every modal loop. The time is measured between every loop to get an idea of the FPS speed, and then this is shown in the area's header. **Exact steps for others to reproduce the error** You should repeat this test in Blender 3.5 and 3.4: - Open the blendfile - Run the script in the Text Editor - Put the cursor in the Image Editor with the Render Result image selected - Press F3 to search and run the operator "test.test". The FPS is now shown in the area's header - You can now change the size of the current Image Editor area while running the modal operator, for example, by dragging the area's border to change the size horizontally. This introduces the performance penalty, and you can see the reduction in FPS as the Image area gets bigger. When reducing the Image area, the speed increases again. This doesn't seem to happen in Blender 3.4, or at least it's imperceptible to me. In 3.4, the Image area can even be at fullscreen and I still can't see a reduction in speed, while in 3.5 the CPU works a lot harder and I can only get the same performance when reducing the size of the area up to a quarter compared to the original from 3.4. - Exit the modal loop with Esc key What's the significance for the time it takes to set a render slot you may ask, and the thing is that I have a script that can change the slots rapidly, temporarily generating an animation with them, without having to export or save the frames. In the current state, it has just became too slow for that.
chaos added the
Priority
Normal
Type
Report
Status
Needs Triage
labels 2023-04-21 00:09:40 +02:00
Member

Hi, thanks for the report. Maybe this is fixed already along with #106092
Can you check again in 3.6 build?: https://builder.blender.org/download/daily/

Hi, thanks for the report. Maybe this is fixed already along with #106092 Can you check again in 3.6 build?: https://builder.blender.org/download/daily/
Pratik Borhade added
Status
Needs Information from User
and removed
Status
Needs Triage
labels 2023-04-21 08:05:03 +02:00
Author
Member

I can confirm that the performance has come back to normal in current 3.6 build.
No noticeable difference with 3.4.
Problem solved, thank you so much!

I can confirm that the performance has come back to normal in current 3.6 build. No noticeable difference with 3.4. Problem solved, thank you so much!
Member

Closing then.

Closing then.
Blender Bot added
Status
Archived
and removed
Status
Needs Information from User
labels 2023-04-22 05:27:25 +02:00
Pratik Borhade added
Status
Resolved
and removed
Status
Archived
labels 2023-04-22 05:27:34 +02: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
2 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#107200
No description provided.