Very slow rendering on RTX 3080! #103450

New Issue

Kostya · 2022-12-24T12:13:39+01:00

Kostya commented

2022-12-24 12:13:39 +01:00

System Information
Operating system: windows 11
Graphics card: RXT 3080 (Gainward RTX 3080 Chasing Wind)

Blender Version
Broken: 3.4.1; 3.4; 3.3.1
Worked: Works on the vega 11 video card built into the processor, also works stably on the CPU. Works on RTX 3080 graphics card with driver 497.29 on all blender versions

Short description of error
At times while working in the blender program, I encounter absurdly long render times for one frame: https://i.imgur.com/oB4BJ5L.png (shreenshot).

I ran render tests on different driver versions (527.56, 522.30, 526.86, 497.29). In all versions of the drivers, after some time, performance dropped hundreds of times, except for driver 497.29. It works stably. Also tests were carried out on blender versions 3.3, 3.4, 3.4.1.

It would seem that the problem is solved, you can simply install the 497.29 driver and work stably on it, but this is not so. Only blender works on this driver version, other programs crash and require drivers of at least 520. Regardless of the driver version, the video card is always loaded at 100%

I've done some testing and may have found what's wrong. I made a scene with several cubes, a volume and a strong light source, and also set a large sample size.
Results:
497.29 driver - 4 minutes 12 seconds (806 MB of video memory used)
527.56 driver - 3 minutes 45 seconds (806 MB of video memory used)
At the same time, the viewport works quickly and responsively in the cycles render mode. Just like I planned
I also ran a test with a complex scene and then everything got much worse:
497.29 driver - 22 minutes 51 seconds (8775 MB VRAM used)
527.56 driver - 35 minutes 37 seconds (8775 MB of video memory used)
The viewport is quite buggy and poorly responsive in both versions of the drivers (but this is logical since the scene is complex). In the viewport, the view mode in cycles on the 497.29 driver works as expected - it gradually develops the picture. On the 527.56 driver, cycles almost doesn't work in the cycles view mode (more precisely, it works, but it's even slower than my four-core processor).
In render mode 527.56 the driver is unstable. I had to wait 11 minutes for the first sample to load. And I'm still lucky. Sometimes the render time can be 44 hours for a single frame (https://i.imgur.com/oB4BJ5L.png)

As a result, we can come to the conclusion that with the new drivers, the blender is unstable when the video memory is almost completely loaded.

I recorded the workflow of all tests on video in an accelerated version: https://drive.google.com/drive/folders/1_oMmj90PLXiojBbORk8W1ynpdzITi6gJ?usp=share_link . I advise you to download the video to your computer so that it does not compress when viewed through Google Drive ...

Exact steps for others to reproduce the error

Make a complex scene with lots of textures, lots of geometry and use the latest Nvidia drivers.
Engage in scene editing often switching between working scenes
Start rendering the scene at a high resolution and a lot of sampling
I made a screen recording of the editing process: https://drive.google.com/drive/folders/1_oMmj90PLXiojBbORk8W1ynpdzITi6gJ?usp=share_link
.blend: https://drive.google.com/drive/folders/1MY37OWlYleiusnEbxDuTwIx63F_eQIVK?usp=share_link

**System Information** Operating system: windows 11 Graphics card: RXT 3080 (Gainward RTX 3080 Chasing Wind) **Blender Version** Broken: 3.4.1; 3.4; 3.3.1 Worked: Works on the vega 11 video card built into the processor, also works stably on the CPU. Works on RTX 3080 graphics card with driver 497.29 on all blender versions **Short description of error** At times while working in the blender program, I encounter absurdly long render times for one frame: https://i.imgur.com/oB4BJ5L.png (shreenshot). I ran render tests on different driver versions (527.56, 522.30, 526.86, 497.29). In all versions of the drivers, after some time, performance dropped hundreds of times, except for driver 497.29. It works stably. Also tests were carried out on blender versions 3.3, 3.4, 3.4.1. It would seem that the problem is solved, you can simply install the 497.29 driver and work stably on it, but this is not so. Only blender works on this driver version, other programs crash and require drivers of at least 520. Regardless of the driver version, the video card is always loaded at 100% I've done some testing and may have found what's wrong. I made a scene with several cubes, a volume and a strong light source, and also set a large sample size. Results: 497.29 driver - 4 minutes 12 seconds (806 MB of video memory used) 527.56 driver - 3 minutes 45 seconds (806 MB of video memory used) At the same time, the viewport works quickly and responsively in the cycles render mode. Just like I planned I also ran a test with a complex scene and then everything got much worse: 497.29 driver - 22 minutes 51 seconds (8775 MB VRAM used) 527.56 driver - 35 minutes 37 seconds (8775 MB of video memory used) The viewport is quite buggy and poorly responsive in both versions of the drivers (but this is logical since the scene is complex). In the viewport, the view mode in cycles on the 497.29 driver works as expected - it gradually develops the picture. On the 527.56 driver, cycles almost doesn't work in the cycles view mode (more precisely, it works, but it's even slower than my four-core processor). In render mode 527.56 the driver is unstable. I had to wait 11 minutes for the first sample to load. And I'm still lucky. Sometimes the render time can be 44 hours for a single frame (https://i.imgur.com/oB4BJ5L.png) As a result, we can come to the conclusion that with the new drivers, the blender is unstable when the video memory is almost completely loaded. I recorded the workflow of all tests on video in an accelerated version: https://drive.google.com/drive/folders/1_oMmj90PLXiojBbORk8W1ynpdzITi6gJ?usp=share_link . I advise you to download the video to your computer so that it does not compress when viewed through Google Drive ... **Exact steps for others to reproduce the error** 1. Make a complex scene with lots of textures, lots of geometry and use the latest Nvidia drivers. 2. Engage in scene editing often switching between working scenes 3. Start rendering the scene at a high resolution and a lot of sampling I made a screen recording of the editing process: https://drive.google.com/drive/folders/1_oMmj90PLXiojBbORk8W1ynpdzITi6gJ?usp=share_link .blend: https://drive.google.com/drive/folders/1MY37OWlYleiusnEbxDuTwIx63F_eQIVK?usp=share_link

Kostya commented

2022-12-24 12:13:39 +01:00

Added subscriber: @Netiks

Pratik Borhade commented

2022-12-27 10:34:54 +01:00

Added subscriber: @PratikPB2123

Philipp Oeser commented

2023-01-03 10:18:58 +01:00

Added subscribers: @pmoursnv, @lichtwerk

Philipp Oeser commented

2023-01-03 10:18:58 +01:00

@pmoursnv : are you aware of driver changes that could cause such a slowdown? Could you possibly test this?

Richard Antalik commented

2023-01-05 09:54:16 +01:00

Added subscriber: @iss

Richard Antalik commented

2023-01-05 09:54:16 +01:00

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

Richard Antalik commented

2023-01-05 09:54:16 +01:00

I can't reproduce this issue. @Netiks do you overclock your GPU?

Operating system: Windows-10-10.0.19041-SP0 64 Bits
Graphics card: NVIDIA GeForce RTX 3060/PCIe/SSE2 NVIDIA Corporation 4.5.0 NVIDIA 526.98

I can't reproduce this issue. @Netiks do you overclock your GPU? Operating system: Windows-10-10.0.19041-SP0 64 Bits Graphics card: NVIDIA GeForce RTX 3060/PCIe/SSE2 NVIDIA Corporation 4.5.0 NVIDIA 526.98

Kostya commented

2023-01-05 11:20:09 +01:00

Good afternoon. I haven't overclocked my GPU. But my GPU has a built-in protection against mining (LHR). Can she mistakenly consider rendering to be mining?

Do you need more information about the system? I can provide everything you need to solve this problem

Good afternoon. I haven't overclocked my GPU. But my GPU has a built-in protection against mining (LHR). Can she mistakenly consider rendering to be mining? Do you need more information about the system? I can provide everything you need to solve this problem

Richard Antalik commented

2023-01-06 13:39:49 +01:00

In #103450#1469526, @Netiks wrote:
But my GPU has a built-in protection against mining (LHR). Can she mistakenly consider rendering to be mining?

I don't think so, just you mentioned instability which can be result of overclocking. Even though you mentioned instability with VRAM being "almost completely loaded", which is quite expected, but with provided file VRAM usage wasn't really high even on my 3060, so not quite sure about this point.

> In #103450#1469526, @Netiks wrote: > But my GPU has a built-in protection against mining (LHR). Can she mistakenly consider rendering to be mining? I don't think so, just you mentioned instability which can be result of overclocking. Even though you mentioned instability with VRAM being "almost completely loaded", which is quite expected, but with provided file VRAM usage wasn't really high even on my 3060, so not quite sure about this point.

Richard Antalik commented

2023-01-06 13:40:00 +01:00

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

Philipp Oeser removed the

Download

What's New

Blender Studio

Manual

Developers Blog

Documentation

Benchmark

Blender Conference

Development Fund

One-time Donations

Very slow rendering on RTX 3080! #103450