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

New Issue

Ludvik Koutny · 2019-02-13T13:39:20+01:00

Ludvik Koutny commented

2019-02-13 13:39:20 +01:00

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.

👍 1

Ludvik Koutny commented

2019-02-13 13:39:20 +01:00

Added subscriber: @Rawalanche

Brecht Van Lommel commented

2019-02-13 13:56:24 +01:00

Added subscriber: @brecht

Brecht Van Lommel commented

2019-02-13 13:56:24 +01:00

Changed status from 'Open' to: 'Archived'

😕 1

Brecht Van Lommel closed this issue

2019-02-13 13:56:24 +01:00

Brecht Van Lommel self-assigned this 2019-02-13 13:56:24 +01:00

Brecht Van Lommel commented

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.

Ludvik Koutny commented

2019-02-13 14:04:27 +01:00

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?

👍 2

Ben Rugg commented

2020-09-28 22:21:49 +02:00

Added subscriber: @benrugg

Ben Rugg commented

2020-09-28 22:22:36 +02:00

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

Jason commented

2024-06-27 01:19:13 +02: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.

The entire reason tile size was introduced was as an optimization. If your optimization has an edge case that makes performance an order of magnitude worse, that's a bug. This is a massive regression in usability from versions before tile size.

> 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. The entire reason tile size was introduced was as an optimization. If your optimization has an edge case that makes performance an order of magnitude worse, that's a bug. This is a massive regression in usability from versions before tile size.

Brecht Van Lommel commented

2024-06-27 01:46:17 +02:00

This was addressed quite a while ago:
https://developer.blender.org/docs/release_notes/3.0/cycles/#tiles-memory-usage

Also, the optimization I was referring to was rendering multiple small tiles at once, not tiles in general. There also exists no version before tile size, tiles were always there.

This was addressed quite a while ago: https://developer.blender.org/docs/release_notes/3.0/cycles/#tiles-memory-usage Also, the optimization I was referring to was rendering multiple small tiles at once, not tiles in general. There also exists no version before tile size, tiles were always there.

Sign in to join this conversation.

No Label

Download

What's New

Blender Studio

Manual

Developers Blog

Documentation

Benchmark

Blender Conference

Development Fund

One-time Donations

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