Big performance difference between console and GUI rendering at large tile size #47071
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
4 Participants
Notifications
Due Date
No due date set.
Dependencies
No dependencies set.
Reference: blender/blender#47071
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
Windows 7 64bit
Intel i7 4Ghz
Nvidia GTX 770 with latest CUDA drivers
16GB RAM
Blender Version
2.76
Short description of error
Certain scenes rendered at large tile size takes an enormously long time to render from the Blender Interface, while it can render at 3x-5x the speed from the command line.
Exact steps for others to reproduce the error
Troubleshooting
Conclusion:
I believe the inefficiency is at displaying the rendered result when the tile size is big. It's expected that console rendering is faster than from the GUI, but I think the performance gap is a little too big here.
renderBug.blend
Changed status to: 'Open'
Added subscriber: @MikePan
Added subscriber: @Brachi
Added subscriber: @Sergey
Hi Sergey,
I am not rendering on a dedicated card. The one GTX770 is used for both display and rendering.
But aha! Switching to GLSL image draw completely fixes the performance issue. It's now rendering as fast as the console. Any explaination why that is?
Added subscriber: @mont29
Changed status from 'Open' to: 'Archived'
Probably because GLSL image drawing is better optimized and/or implies less exchanges between system and GPU memory?
Anyway, think we can say issue is fixed, so closing it for now.
It's nothing much to do with exchanges actually. Rendering in the interface will almost always be slower because of need of doing color management of the render result while rendering. Thing is, on every tile update the displayed image s being refreshed (converted from linear space in which renderer works to a display space which is usually sRGB) which takes some CPU power. When using GLSL image draw method conversion is happening on the GPU and if you're rendering on CPU then you'll have much less impact on the render time.
Rendering in the background does not update display buffer (there's nothing to display) and hence it's faster.
Surely we might start doing things like skipping tile update all together or making it so they're only updated every so often, but it's all a bit fuzzy and conflicts with the desire of artists to see everything immediately. So for now just use GLSL image drawing if it works fine for you.