OIDN: RAM increases proportionally with each Denoise node used #69006

New Issue

YAFU · 2019-08-21T19:21:12+02:00

YAFU commented

2019-08-21 19:21:12 +02:00

System Information
Operating system: Linux-5.0.1-050001-generic-x86_64-with-debian-buster-sid 64 Bits
Graphics card: GeForce GTX 960/PCIe/SSE2 NVIDIA Corporation 4.5.0 NVIDIA 430.40

Blender Version
Broken: version: 2.81 (sub 2), branch: master, commit date: 2019-08-20 18:26, hash: b6b01c48fa
Worked: (optional)

Hello
Apparently RAM increases proportionally with each Denoise node used in compositor:
Denoise RAM_1.blend
Denoise RAM_2.blend

Denoise RAM_1.blend - 2.2GiB
Denoise RAM_2.blend - 13GiB

We are not sure about whether this is an expected behavior or a bug:
https://blenderartists.org/t/big-denoise-test-intel-open-image-denoise-vs-others/1175114/46

**System Information** Operating system: Linux-5.0.1-050001-generic-x86_64-with-debian-buster-sid 64 Bits Graphics card: GeForce GTX 960/PCIe/SSE2 NVIDIA Corporation 4.5.0 NVIDIA 430.40 **Blender Version** Broken: version: 2.81 (sub 2), branch: master, commit date: 2019-08-20 18:26, hash: `b6b01c48fa` Worked: (optional) Hello Apparently RAM increases proportionally with each Denoise node used in compositor: [Denoise RAM_1.blend](https://archive.blender.org/developer/F7682181/Denoise_RAM_1.blend) [Denoise RAM_2.blend](https://archive.blender.org/developer/F7682340/Denoise_RAM_2.blend) Denoise RAM_1.blend - 2.2GiB Denoise RAM_2.blend - 13GiB We are not sure about whether this is an expected behavior or a bug: https://blenderartists.org/t/big-denoise-test-intel-open-image-denoise-vs-others/1175114/46

YAFU commented

2019-08-21 19:21:13 +02:00

Added subscriber: @YAFU

Stefan Werner was assigned by Brecht Van Lommel

2019-08-21 19:32:05 +02:00

Stefan Werner commented

2019-08-23 16:36:35 +02:00

The compositor is running separate threads for independent nodes. In most constellations, that means that all denoising nodes run at the same time.

Since OIDN internally is multithreaded across all CPU cores, should we wrap it in a mutex to ensure only one denoising kernel runs at a time?

The compositor is running separate threads for independent nodes. In most constellations, that means that all denoising nodes run at the same time. Since OIDN internally is multithreaded across all CPU cores, should we wrap it in a mutex to ensure only one denoising kernel runs at a time?

Brecht Van Lommel commented

2019-08-23 16:37:50 +02:00

Added subscriber: @brecht

Brecht Van Lommel commented

2019-08-23 16:37:50 +02:00

Mutex sounds like a good solution to me.

Stefan Werner commented

2019-08-27 11:07:40 +02:00

Changed status from 'Open' to: 'Resolved'

Stefan Werner closed this issue

2019-08-27 11:07:40 +02:00

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

OIDN: RAM increases proportionally with each Denoise node used #69006