Am 24.05.2018 um 21:51 schrieb Ulrich Pegelow: > Am 24.05.2018 um 18:15 schrieb Matthias Bodenbinder: >> Am 24.05.2018 um 17:43 schrieb Matthias Bodenbinder: >>> 37,787315 [opencl_summary_statistics] device 'GeForce GTX 1050 Ti' (0): >>> peak memory usage 3807805440 bytes >>> 37,787326 [opencl_summary_statistics] device 'GeForce GTX 1050 Ti' (0): 499 >>> out of 500 events were successful and 1 events lost >>> >> > Peak memory usage is at 3632MB which is 400MB below your GPUs total of > 4032MB, as to be expected due to your setting of opencl_memory_headroom=400. > > Intermediately you have > > +-----------------------------------------------------------------------------+ > | NVIDIA-SMI 396.24 Driver Version: 396.24 | > |-------------------------------+----------------------+----------------------+ > | GPU Name Persistence-M| Bus-Id Disp.A | Volatile Uncorr. ECC > | > Fan Temp Perf Pwr:Usage/Cap| Memory-Usage | GPU-Util Compute M. | > |===============================+======================+======================| > | 0 GeForce GTX 105... Off | 00000000:01:00.0 On | N/A | > | 21% 47C P0 N/A / 75W | 365MiB / 4032MiB | 0% Default | > +-------------------------------+----------------------+----------------------+ > > which is really close to 400MB. Note that darktable (as any program using > opencl) has no means to detect the free amount of GPU memory at any time, so > it relies on having access to all minus opencl_memory_headroom. > > I suggest to set a significantly higher value for opencl_memory_headroom like > 800 or even higher in your case. You have a lot of memory, no problem to be a > bit more permissive. > > Ulrich > ____________________________________________________________________________ > darktable user mailing list > to unsubscribe send a mail to [email protected] > >
I did set opencl_memory_headroom=700 now. But for me the issue is more: Why does it work with opencl_memory_headroom=400 for the first couple of cycles and then I get the issue. Then I increase the value to opencl_memory_headroom=500 which fixes it for a while before it happens again and I need to go to opencl_memory_headroom=600 and so forth. That means that the memory problem is getting worse over time. But why? Is that a memory leak? ____________________________________________________________________________ darktable user mailing list to unsubscribe send a mail to [email protected]
