Cycles Tile Size has extreme impact on texture baking performance without any difference in baked texture quality #61509

Closed
opened 2019-02-13 13:39:20 +01:00 by Ludvik Koutny · 7 comments
Contributor

System Information
Operating system: Windows 10
Graphics card: GTX1080Ti

Blender Version
Broken: 2.8 latest master

Short description of error
When baking textures with Cycles, increasing tile size significantly decreases texture bake rendering time without any impact on resulting baked texture quality. This signifies extreme inefficiency of texture baking in Cycles with default setting of tile size at 32.

Exact steps for others to reproduce the error
1, Make sure you have nVidia GPU enabled as CUDA device in Preferences
2, Grab the scene here: https://drive.google.com/open?id=1fvrpnFcg4vClbmPdNwncw3nR9GeoLfJb
3, Open the scene, make sure BakeTest Image Texture is selected in the node view, and click the Bake button in Cycles render settings
4, Observe the long bake rendering time (2:04 minutes in my case)
5, Once bake is done, save the baked BakeTest image from the Image View editor for comparison later.
6, In Cycles render settings panel, increase Tile Size parameters from 32x32 to 1024x1024 (The size of the baked texture)
7, Click the bake button again and observe the short rendertime (0:08 minutes in my case)
8, Once bake is done, save the BakeTest image again for comparison with previous one.
9, Compare the both saved images.

Result: With tile size set to default 32x32, baking of the texture takes 15.5x longer than with tile size set to resolution of the baked texture, yet there is no difference in the baked texture quality which would justify almost 16x longer rendertime.

Expected: Cycles will always bake textures at optimal performance, regardless of tile size.

**System Information** Operating system: Windows 10 Graphics card: GTX1080Ti **Blender Version** Broken: 2.8 latest master **Short description of error** When baking textures with Cycles, increasing tile size significantly decreases texture bake rendering time without any impact on resulting baked texture quality. This signifies extreme inefficiency of texture baking in Cycles with default setting of tile size at 32. **Exact steps for others to reproduce the error** 1, Make sure you have nVidia GPU enabled as CUDA device in Preferences 2, Grab the scene here: https://drive.google.com/open?id=1fvrpnFcg4vClbmPdNwncw3nR9GeoLfJb 3, Open the scene, make sure BakeTest Image Texture is selected in the node view, and click the Bake button in Cycles render settings 4, Observe the long bake rendering time (2:04 minutes in my case) 5, Once bake is done, save the baked BakeTest image from the Image View editor for comparison later. 6, In Cycles render settings panel, increase Tile Size parameters from 32x32 to 1024x1024 (The size of the baked texture) 7, Click the bake button again and observe the short rendertime (0:08 minutes in my case) 8, Once bake is done, save the BakeTest image again for comparison with previous one. 9, Compare the both saved images. Result: With tile size set to default 32x32, baking of the texture takes 15.5x longer than with tile size set to resolution of the baked texture, yet there is no difference in the baked texture quality which would justify almost 16x longer rendertime. Expected: Cycles will always bake textures at optimal performance, regardless of tile size.
Author
Contributor

Added subscriber: @Rawalanche

Added subscriber: @Rawalanche

Added subscriber: @brecht

Added subscriber: @brecht

Changed status from 'Open' to: 'Archived'

Changed status from 'Open' to: 'Archived'
Brecht Van Lommel self-assigned this 2019-02-13 13:56:24 +01:00

We are aware of this issue, it can use an optimization similar to rendering to better work with small tile sizes. But this is outside the scope of the bug tracker.

We are aware of this issue, it can use an optimization similar to rendering to better work with small tile sizes. But this is outside the scope of the bug tracker.
Author
Contributor

In #61509#619751, @brecht wrote:
We are aware of this issue, it can use an optimization similar to rendering to better work with small tile sizes. But this is outside the scope of the bug tracker.

So 16x slower rendertime by default for 1k texture baking is fine, given that most users probably aren't aware of it? To me, that falls well into the territory of a bug, rather than limitation. If it's too difficult to solve, wouldn't it make sense to perform at least temporary fix of internally setting tile size to the size of baked texture every time bake is performed?

> In #61509#619751, @brecht wrote: > We are aware of this issue, it can use an optimization similar to rendering to better work with small tile sizes. But this is outside the scope of the bug tracker. So 16x slower rendertime by default for 1k texture baking is fine, given that most users probably aren't aware of it? To me, that falls well into the territory of a bug, rather than limitation. If it's too difficult to solve, wouldn't it make sense to perform at least temporary fix of internally setting tile size to the size of baked texture every time bake is performed?

Added subscriber: @benrugg

Added subscriber: @benrugg

I just became aware of this issue. Is there a place it should be posted, if it's not considered a bug?

I just became aware of this issue. Is there a place it should be posted, if it's not considered a bug?
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
3 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#61509
No description provided.