Disproportional Render Time approaching 16k Environment Textures on CUDA Device #78033

New Issue

Erik · 2020-06-19T11:35:35+02:00

Erik commented

2020-06-19 11:35:35 +02:00

System Information
Operating system: Windows 10
Graphics card: GTX 980Ti

Blender Version
2.8

Short description of error
CUDA GPU render time increases drastically when switching from a nearly 16k environment texture (13824x7776) to 16k (15380x8640) in Cycles. In the first case, rendering finishes in 13 seconds for me, the latter takes 55 seconds. "Updating Lights | Importance Map" alone takes longer than the entire first render. This behaviour does not occur when using a CPU.

The issue might not be a "real" bug, it just renders GPUs useless for this scenario and with 16k HDRIs being largely available on sites like HDRI Haven, it might be a problem in the future.

Exact steps for others to reproduce the error
Open the .blend file and switch between nearly_16k.jpg (81% 16k pixel count) and 16k.jpg environment textures (rendering on CUDA Device)
You can use any other picture obviously. The difference between an 8k image and the nearly_16k one is negligible.

test.blend

**System Information** Operating system: Windows 10 Graphics card: GTX 980Ti **Blender Version** 2.8 **Short description of error** CUDA GPU render time increases drastically when switching from a nearly 16k environment texture (13824x7776) to 16k (15380x8640) in Cycles. In the first case, rendering finishes in 13 seconds for me, the latter takes 55 seconds. "Updating Lights | Importance Map" alone takes longer than the entire first render. This behaviour does not occur when using a CPU. The issue might not be a "real" bug, it just renders GPUs useless for this scenario and with 16k HDRIs being largely available on sites like HDRI Haven, it might be a problem in the future. **Exact steps for others to reproduce the error** Open the .blend file and switch between nearly_16k.jpg (81% 16k pixel count) and 16k.jpg environment textures (rendering on CUDA Device) You can use any other picture obviously. The difference between an 8k image and the nearly_16k one is negligible. [test.blend](https://archive.blender.org/developer/F8631892/test.blend) ![nearly_16k.jpg](https://archive.blender.org/developer/F8631891/nearly_16k.jpg) ![16k.jpg](https://archive.blender.org/developer/F8631890/16k.jpg)

Erik commented

2020-06-19 11:35:35 +02:00

Added subscriber: @ElrikLeBaum

Alaska commented

2020-06-19 12:39:38 +02:00

Added subscriber: @Alaska

Alaska commented

2020-06-19 12:39:38 +02:00

Can confirm when testing with a GTX 1050Ti. However, testing with my friend's RTX 2070 Super I can not reproduce.

This is either a bug in CUDA with older GPUs or a VRAM limitation.

Can confirm when testing with a GTX 1050Ti. However, testing with my friend's RTX 2070 Super I can not reproduce. This is either a bug in CUDA with older GPUs or a VRAM limitation.

Ankit Meel commented

2021-04-18 12:43:26 +02:00

Added subscriber: @ankitm

Ankit Meel commented

2021-04-18 12:43:26 +02:00

Changed status from 'Needs Triage' to: 'Needs User Info'

Ankit Meel commented

2021-04-18 12:43:26 +02:00

Please test on a recent Blender version.

Philipp Oeser commented

2021-05-28 17:01:38 +02:00

Added subscriber: @lichtwerk

Philipp Oeser commented

2021-05-28 17:01:39 +02:00

Cannot reproduce on a 970m in a recent build (11sec vs 12sec).

So everyone please try this in a fresh build and report back if this is still an issue

Cannot reproduce on a 970m in a recent build (11sec vs 12sec). So everyone please try this in a fresh build and report back if this is still an issue

Philipp Oeser commented

2021-07-02 12:10:18 +02:00

Changed status from 'Needs User Info' to: 'Archived'

Philipp Oeser closed this issue

2021-07-02 12:10:18 +02:00

Philipp Oeser commented

2021-07-02 12:10:18 +02:00

No activity for more than a week. As per the tracker policy we assume the issue is gone and can be closed.

Thanks again for the report. If the problem persists please open a new report with the required information.

No activity for more than a week. As per the tracker policy we assume the issue is gone and can be closed. Thanks again for the report. If the problem persists please open a new report with the required information.

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

Disproportional Render Time approaching 16k Environment Textures on CUDA Device #78033